| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | zstd compression for pg_dump |
| Date: | 2020-12-21 19:49:24 |
| Message-ID: | 20201221194924.GI30237@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I found that our largest tables are 40% smaller and 20% faster to pipe
pg_dump -Fc -Z0 |zstd relative to native zlib
So I wondered how much better when integrated in pg_dump, and found that
there's some additional improvement, but a big disadvantage of piping through
zstd is that it's not identified as a PGDMP file, and, /usr/bin/file on centos7
fails to even identify zstd by its magic number..
I looked for previous discussion about alternate compressions, but didn't find
anything for pg_dump.
--
Justin
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-fix-pre-existing-docs-comments.patch | text/x-diff | 1.8 KB |
| 0002-Fix-malformed-comment.patch | text/x-diff | 1.2 KB |
| 0003-pg_dump-zstd-compression.patch | text/x-diff | 29.9 KB |
| 0004-cmdline-parser-for-compression-alg-level-opts.patch | text/x-diff | 242.3 KB |
| 0005-union-with-a-CompressionAlgorithm-alg.patch | text/x-diff | 11.6 KB |
| 0006-Move-zlib-into-the-union.patch | text/x-diff | 4.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-21 20:02:40 | Re: zstd compression for pg_dump |
| Previous Message | Stephen Frost | 2020-12-21 19:13:39 | Re: BUG #16079: Question Regarding the BUG #16064 |