News for hackers. Stuff that matters.

A comment on When to Avoid JSONB in a PostgreSQL Schema. Parent comment

Re:When to Avoid JSONB in a PostgreSQL Schema by ngrilly on Friday September 02, 2016 @05:11PM (#12416321)
Thanks Michael for clearing my doubts :-)

One last question: I guess most queries target a time range. Do you use BRIN indexes to avoid scanning the whole 800 MB of data in each shard, and just read the necessary pages?

[ Parent | on HN ]
Re:When to Avoid JSONB in a PostgreSQL Schema by malisper on Friday September 02, 2016 @05:54PM (#12416552)
That get's into our indexing strategy which Dan talks about in this talk[0]. Currently our tables aren't completely insert only, so a BRIN index wouldn't work for us, as one row in the wrong place can cause a huge amount of extra reads.

[0] https://www.youtube.com/watch?v=NVl9_6J1G60

[ Parent | on HN ]
Re:When to Avoid JSONB in a PostgreSQL Schema by ngrilly on Monday September 05, 2016 @08:51AM (#12429916)
No more question :-) Thanks Michael for you time, and for the link to Dan's talk. It's great to see how, at Heap, you scaled a multitenant SaaS based on PostgreSQL!
[ Parent | on HN ]