| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pglz compression performance, take two |
| Date: | 2021-06-25 07:31:17 |
| Message-ID: | YNWGRfZxneqhDtFS@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 20, 2021 at 12:19:45AM -0500, Justin Pryzby wrote:
> I think it's still relevant, since many people may not end up with binaries
> --with-lz4 (I'm thinking of cloud providers). PGLZ is what existing data uses,
> and people may not want to/know to migrate to shiny new features, but they'd
> like it if their queries were 20% faster after upgrading without needing to.
Yeah, I agree that local improvements here are relevant, particularly
as we don't enforce the rewrite of toast data already compressed with
pglz. So, we still need to stick with pglz for some time.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-06-25 08:00:23 | Re: alter subscription drop publication fixes |
| Previous Message | Boris Kolpackov | 2021-06-25 07:13:53 | Re: Pipeline mode and PQpipelineSync() |