From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
Subject: | Re: head fails to build on SLES 12 (wal_compression=zstd) |
Date: | 2022-03-31 23:38:29 |
Message-ID: | 898147.1648769909@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Thu, Mar 31, 2022 at 11:44:40AM -0400, Tom Lane wrote:
>> In view of 51c0d186d ("Allow parallel zstd compression"), I agree
>> that some clarity about the minimum supported version of zstd
>> seems essential. I don't want to be dealing with threading bugs
>> in ancient zstd versions. However, why do you suggest 1.3.7 in
>> particular?
> That's where I found that ZSTD_CLEVEL_DEFAULT was added, in their git.
> I've just installed a .deb for 1.3.8, and discovered that the APIs used by
> basebackup were considered experimental/nonpublic/static-lib-only until 1.4.0
Indeed. I tried building against 1.3.6 (mainly because it was laying
around) and the error reported by Devrim is just the tip of the iceberg.
With "make -k", I see unknown-symbol failures on
ZSTD_CCtx_setParameter
ZSTD_c_compressionLevel
ZSTD_c_nbWorkers
ZSTD_CCtx_reset
ZSTD_reset_session_only
ZSTD_compressStream2
ZSTD_e_continue
ZSTD_e_end
I wonder whether Robert's ambition to be compatible with old versions
extends that far.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bradley Ayers | 2022-03-31 23:39:06 | [WIP] ALTER COLUMN IF EXISTS |
Previous Message | David G. Johnston | 2022-03-31 23:36:05 | Re: unlogged sequences |