Re: multithreaded zstd backup compression for client and server - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: multithreaded zstd backup compression for client and server
Date
Msg-id 20220323215234.GX28503@telsasoft.com
Whole thread Raw
In response to multithreaded zstd backup compression for client and server  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: multithreaded zstd backup compression for client and server  (Robert Haas <robertmhaas@gmail.com>)
fixing a few backup compression goofs  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
+        * We check for failure here because (1) older versions of the library
+        * do not support ZSTD_c_nbWorkers and (2) the library might want to
+        * reject an unreasonable values (though in practice it does not seem to do
+        * so).
+        */
+       ret = ZSTD_CCtx_setParameter(mysink->cctx, ZSTD_c_nbWorkers,
+                                                                mysink->workers);
+       if (ZSTD_isError(ret))
+               ereport(ERROR,
+                               errcode(ERRCODE_INVALID_PARAMETER_VALUE),
+                               errmsg("could not set compression worker count to %d: %s",
+                                          mysink->workers, ZSTD_getErrorName(ret)));

Also because the library may not be compiled with threading.  A few days ago, I
tried to rebase the original "parallel workers" patch over the COMPRESS DETAIL
patch but then couldn't test it, even after trying various versions of the zstd
package and trying to compile it locally.  I'll try again soon...

I think you should also test the return value when setting the compress level.
Not only because it's generally a good idea, but also because I suggested to
support negative compression levels.  Which weren't allowed before v1.3.4, and
then the range is only defined since 1.3.6 (ZSTD_minCLevel).  At some point,
the range may have been -7..22 but now it's -131072..22.

lib/compress/zstd_compress.c:int ZSTD_minCLevel(void) { return (int)-ZSTD_TARGETLENGTH_MAX; }
lib/zstd.h:#define ZSTD_TARGETLENGTH_MAX    ZSTD_BLOCKSIZE_MAX
lib/zstd.h:#define ZSTD_BLOCKSIZE_MAX     (1<<ZSTD_BLOCKSIZELOG_MAX)
lib/zstd.h:#define ZSTD_BLOCKSIZELOG_MAX  17
; -1<<17
        -131072

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: MDAM techniques and Index Skip Scan patch
Next
From: Dmitry Dolgov
Date:
Subject: Re: MDAM techniques and Index Skip Scan patch