From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | f(dot)pardi(at)portavita(dot)eu, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL VS MongoDB: a use case comparison |
Date: | 2018-11-20 19:46:59 |
Message-ID: | 20181120194659.GJ3415@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Greetings,
* Merlin Moncure (mmoncure(at)gmail(dot)com) wrote:
> On Tue, Nov 20, 2018 at 11:28 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Oh yes, having a dictionary would be a great start to reducing the size
> > of the jsonb data, though it could then become a contention point if
> > there's a lot of new values being inserted and such. Naturally there
> > would also be a cost to pulling that data back out as well but likely it
> > would be well worth the benefit of not having to store the field names
> > repeatedly.
>
> Yes, the biggest concern with a shared dictionary ought to be
> concurrency type problems.
Hmmm, I wonder if we could do something like have a dictionary per
page.. Or perhaps based on some hash of the toast ID.. Not sure. :)
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2018-11-21 06:48:05 | Re: PostgreSQL VS MongoDB: a use case comparison |
Previous Message | Merlin Moncure | 2018-11-20 19:45:02 | Re: PostgreSQL VS MongoDB: a use case comparison |