Re: Add LZ4 compression in pg_dump
gkokolatos@pm.me
Attachments
- v19-0001-Prepare-pg_dump-internals-for-additional-compres.patch (text/x-patch) patch v19-0001
- v19-0002-Introduce-Compressor-API-in-pg_dump.patch (text/x-patch) patch v19-0002
- v19-0003-Add-LZ4-compression-in-pg_-dump-restore.patch (text/x-patch) patch v19-0003
------- Original Message ------- On Tuesday, December 20th, 2022 at 4:26 PM, Justin Pryzby <pryzby@telsasoft.com> wrote: > > > On Tue, Dec 20, 2022 at 11:19:15AM +0000, gkokolatos@pm.me wrote: > > > ------- Original Message ------- > > On Monday, December 19th, 2022 at 6:27 PM, Justin Pryzby pryzby@telsasoft.com wrote: > > > > > On Mon, Dec 19, 2022 at 05:03:21PM +0000, gkokolatos@pm.me wrote: > > > > > > > > > 001 still doesn't compile on freebsd, and 002 doesn't compile on > > > > > > windows. Have you checked test results from cirrusci on your private > > > > > > github account ? > > > > > > > > There are still known gaps in 0002 and 0003, for example documentation, > > > > and I have not been focusing too much on those. You are right, it is helpful > > > > and kind to try to reduce the noise. The attached should have hopefully > > > > tackled the ci errors. > > > > > > Yep. Are you using cirrusci under your github account ? > > > > Thank you. To be very honest, I am not using github exclusively to post patches. > > Sometimes I do, sometimes I do not. Is github a requirement? > > > Github isn't a requirement for postgres (but cirrusci only supports > github). I wasn't not trying to say that it's required, only trying to > make sure that you (and others) know that it's available, since our > cirrus.yml is relatively new. Got it. Thank you very much for spreading the word. It is a useful feature which should be known. > > > > > > > 002 breaks "pg_dump -Fc -Z2" because (I think) AllocateCompressor() > > > > > > doesn't store the passed-in compression_spec. > > > > > > > > I am afraid I have not been able to reproduce this error. I tried both > > > > debian and freebsd after I addressed the compilation warnings. Which > > > > error did you get? Is it still present in the attached? > > > > > > It's not that there's an error - it's that compression isn't working. > > > > > > $ ./tmp_install/usr/local/pgsql/bin/pg_dump -h /tmp -Z1 -Fp regression |wc -c > > > 659956 > > > $ ./tmp_install/usr/local/pgsql/bin/pg_dump -h /tmp -Z2 -Fp regression |wc -c > > > 637192 > > > > > > $ ./tmp_install/usr/local/pgsql/bin/pg_dump -h /tmp -Z1 -Fc regression |wc -c > > > 1954890 > > > $ ./tmp_install/usr/local/pgsql/bin/pg_dump -h /tmp -Z2 -Fc regression |wc -c > > > 1954890 > > > > Thank you. Now I understand what you mean. Trying the same on top of v18-0003 > > on Ubuntu 22.04 yields: > > > You're right; this seems to be fixed in v18. Thanks. Great. Still there was a bug in v17 which you discovered. Thank you for the review effort. Please find in the attached v19 an extra check right before calling deflateInit(). This check will verify that only compressed output will be generated for this method. Also v19 is rebased on top f450695e889 and applies cleanly. Cheers. //Georgios > -- > Justin
Commits
-
Advance input pointer when LZ4 compressing data
- 1a05c1d25299 16.0 landed
-
Null-terminate the output buffer of LZ4Stream_gets
- 3c18d90f8907 16.0 landed
-
Rework code defining default compression for dir/custom formats in pg_dump
- bedc1f0564d1 16.0 landed
-
pg_dump: Use only LZ4 frame format for compression
- 0070b66fef21 16.0 landed
-
Minor comment improvements for compress_lz4
- d0160ca11e31 16.0 landed
-
Unify buffer sizes in pg_dump compression API
- f081a48f9a91 16.0 landed
-
Improve type handling in pg_dump's compress file API
- d3b57755e60c 16.0 landed
-
Improve wording in pg_dump compression docs
- 6095069b40d7 16.0 landed
-
Fix condition in pg_dump TAP test
- 34ce11437497 16.0 landed
-
Add LZ4 compression to pg_dump
- 0da243fed087 16.0 landed
-
Introduce a generic pg_dump compression API
- e9960732a961 16.0 landed
-
Prepare pg_dump internals for additional compression methods
- 03d02f54a640 16.0 landed
-
Fix behavior with pg_restore -l and compressed dumps
- 783d8abc3b63 16.0 landed
-
Add 250c8ee07ed to git-blame-ignore-revs
- ff23b592ad66 16.0 cited
-
Provide test coverage in pg_dump for default behaviors with compression
- a7885c9bb22d 16.0 landed
-
Switch pg_dump to use compression specifications
- 5e73a6048849 16.0 landed
-
Refactor code parsing compression option values (-Z/--compress)
- d18655cc037a 16.0 landed
-
meson: Add some missing env settings for tests of pg_dump and pg_verifybackup
- 00ae5d6f588e 16.0 landed
-
Extend TAP tests of pg_dump to test for compression with gzip
- 98fe74218d97 15.0 landed
-
Clean up some dead code in pg_dump with tar format and gzip compression
- 8ac4c25a05d1 15.0 landed
-
Add TAP test in pg_dump with --format=tar and --compress
- edcedcc2c7bb 15.0 landed
-
Replace BASE_BACKUP COMPRESSION_LEVEL option with COMPRESSION_DETAIL.
- ffd53659c46a 15.0 cited
-
Refactor the pg_dump zlib code from pg_backup_custom.c to a separate file,
- bf9aa490db24 9.1.0 cited