Re: sys_siglist[] is causing us trouble again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, rosset(dot)filipe(at)gmail(dot)com
Subject: Re: sys_siglist[] is causing us trouble again
Date: 2020-07-16 00:14:36
Message-ID: 3218392.1594858476@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Thu, Jul 16, 2020 at 10:48 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> We haven't changed anything, ergo something changed at the OS level.

> It looks like glibc very recently decided[1] to hide the declaration,
> but we're using a cached configure test result.

Right. So, modulo the mis-cached result, what would happen if we do
nothing is that the back branches would lose the ability to translate
signal numbers to strings on bleeding-edge glibc. I don't think we
want that, so we need to back-patch. Attached is a lightly tested
patch for v11. (This includes 7570df0f3 as well, so that
pgstrsignal.c will be the same in all branches.)

regards, tom lane

Attachment Content-Type Size
replace-sys_siglist-with-strsignal-v11.patch text/x-diff 12.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-07-16 00:30:12 "cert" + clientcert=verify-ca in pg_hba.conf?
Previous Message Dean Rasheed 2020-07-15 23:39:33 Re: Infinities in type numeric