From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: macos ventura SDK spews warnings |
Date: | 2022-10-16 01:00:00 |
Message-ID: | 1618364.1665882000@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> snprintf is required by POSIX going back to SUSv2, so it's pretty darn
> hard to imagine any currently-used platform that hasn't got it. Even
> my now-extinct dinosaur gaur had it (per digging in backup files).
> I think we could certainly assume its presence in the branches that
> require C99.
After further thought, I think the best compromise is just that:
(1) apply s/sprintf/snprintf/ patch in branches back to v12, where
we began to require C99.
(2) in v11 and back to 9.2, enable -Wno-deprecated if available.
One thing motivating this choice is that we're just a couple
weeks away from the final release of v10. So I'm hesitant to do
anything that might turn out to be moving the portability goalposts
in v10. But we're already assuming we can detect -Wno-foo options
correctly in v10 and older (e.g. 4c5a29c0e), so point (2) seems
pretty low-risk.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-10-16 01:08:15 | Re: New docs chapter on Transaction Management and related changes |
Previous Message | Andres Freund | 2022-10-16 00:14:40 | Re: macos ventura SDK spews warnings |