From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: msys inet_pton strangeness |
Date: | 2024-09-30 15:05:34 |
Message-ID: | c654d3ae-6a03-4281-8935-593d9825d4fb@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-09-30 Mo 10:08 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Ah, so this is because gcc 14.1.0 treats this as an error but gcc 12.2.0
>> treats it as a warning. Now it makes sense.
> Not entirely ... if fairywren had been generating that warning all
> along, I would have noticed it long ago, because I periodically
> scrape the BF database for compiler warnings. There has to have
> been some recent change in the system include files.
here's what I see on vendikar:
pgbfprod=> select min(snapshot) from build_status_log where log_stage in
('build.log', 'make.log') and branch = 'REL_15_STABLE' and sysname =
'fairywren' and snapshot > now() - interval '1500 days' and log_text ~
'inet_pton';
min
---------------------
2022-06-30 18:04:08
(1 row)
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-09-30 15:05:36 | Re: Do not lock temp relations |
Previous Message | Tom Lane | 2024-09-30 14:55:39 | Re: pg_upgrade check for invalid databases |