From: Stephen Frost <sfrost@snowman.net>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: f.pardi@portavita.eu, postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL VS MongoDB: a use case comparison
Date: Tue, 20 Nov 2018 11:43:25 -0500
Message-ID: <20181120164325.GE3415@tamriel.snowman.net> (raw)
In-Reply-To: <CAHyXU0wQKaoQsZL=adB5vCFhjL+2kn4DiRnmVDEABJC8aCAz0w@mail.gmail.com>
References: <d43fd220-09f7-af4c-2623-44f094b15115@portavita.eu>
<20181119172609.GR3415@tamriel.snowman.net>
<CAHyXU0wQKaoQsZL=adB5vCFhjL+2kn4DiRnmVDEABJC8aCAz0w@mail.gmail.com>
Greetings,
* Merlin Moncure (mmoncure@gmail.com) wrote:
> On Mon, Nov 19, 2018 at 11:26 AM Stephen Frost <sfrost@snowman.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
Attachments:
[application/pgp-signature] signature.asc (818B, ../20181120164325.GE3415@tamriel.snowman.net/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sfrost@snowman.net, mmoncure@gmail.com
Subject: Re: PostgreSQL VS MongoDB: a use case comparison
In-Reply-To: <20181120164325.GE3415@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox