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 16:43:25 |
Message-ID: | 20181120164325.GE3415@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 Mon, Nov 19, 2018 at 11:26 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Looks like a lot of the difference being seen and the comments made
> > about one being faster than the other are because one system is
> > compressing *everything*, while PG (quite intentionally...) only
> > compresses the data sometimes- once it hits the TOAST limit. That
> > likely also contributes to why you're seeing the on-disk size
> > differences that you are.
>
> Hm. It may be intentional, but is it ideal? Employing datum
> compression in the 1kb-8kb range with a faster but less compressing
> algorithm could give benefits.
Well, pglz is actually pretty fast and not as good at compression as
other things. I could certainly see an argument for allowing a column
to always be (or at least attempted to be) compressed.
There's been a lot of discussion around supporting alternative
compression algorithms but making that happen is a pretty big task.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2018-11-20 17:02:53 | Re: PostgreSQL VS MongoDB: a use case comparison |
Previous Message | Merlin Moncure | 2018-11-20 16:41:42 | Re: PostgreSQL VS MongoDB: a use case comparison |