| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Date: | 2024-11-20 15:32:09 |
| Message-ID: | 152145.1732116729@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> Note that if we backpatch C23 support, we also need to backpatch at
> least commits a67a49648d9 and d2b4b4c2259.
Yeah. Our normal theory for this kind of thing is "people are
likely to build our old branches with modern toolchains", so
we are going to have to back-patch C23 compatibility sooner or
later. In fact, we'll have to back-patch to 9.2, or else
decide that those branches are unbuildable on modern platforms
and hence out of scope for compatibility testing.
We have a little bit of grace time before this needs to happen,
but perhaps not very much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-11-20 15:32:47 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
| Previous Message | Bertrand Drouvot | 2024-11-20 15:20:45 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |