Thanks Tushar for the testing. I further worked on ZSTD and now have implemented client side compression as well. Attached are the patches for both server-side and client-side compression.
The patch 0001 is a server-side patch, and has not changed since the last patch version - v10, but, just bumping the version number. Patch 0002 is the client-side compression patch. Regards, Jeevan Ladhe On Tue, 15 Feb 2022 at 22:24, tushar <tushar.ah...@enterprisedb.com> wrote: > On 2/15/22 6:48 PM, Jeevan Ladhe wrote: > > Please find the attached updated version of patch for ZSTD server side > Thanks, Jeevan, I again tested with the attached patch, and as mentioned > the crash is fixed now. > > also, I tested with different labels with gzip V/s zstd against data > directory size which is 29GB and found these results > > ==== > ./pg_basebackup -t server:/tmp/<directory> > --compress=server-zstd:<label> -Xnone -n -N --no-estimate-size -v > > --compress=server-zstd:1 = compress directory size is 1.3GB > --compress=server-zstd:4 = compress directory size is 1.3GB > --compress=server-zstd:7 = compress directory size is 1.2GB > --compress=server-zstd:12 = compress directory size is 1.2GB > ==== > > === > ./pg_basebackup -t server:/tmp/<directooy> > --compress=server-gzip:<label> -Xnone -n -N --no-estimate-size -v > > --compress=server-gzip:1 = compress directory size is 1.8GB > --compress=server-gzip:4 = compress directory size is 1.6GB > --compress=server-gzip:9 = compress directory size is 1.6GB > === > > -- > regards,tushar > EnterpriseDB https://www.enterprisedb.com/ > The Enterprise PostgreSQL Company > >
v11-0001-Add-a-ZSTD-compression-method-for-server-side-compre.patch
Description: Binary data
v11-0002-ZSTD-CLIENT-compression-WIP-working.patch
Description: Binary data
