Re: Build failure with GCC 15 (defaults to -std=gnu23)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robins Tharakan <tharakan@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Thomas Munro <thomas.munro@gmail.com>,
Peter Eisentraut <peter@eisentraut.org>, Sam James <sam@gentoo.org>,
pgsql-bugs@lists.postgresql.org
Date: 2024-12-13T03:42:13Z
Lists: pgsql-bugs
Robins Tharakan <tharakan@gmail.com> writes: > Is it possible that 2 concurrent runs (of different branches) could step on > each other? Looks that way, doesn't it? But I suspect it's just a timing problem --- perhaps one triggered by the background load caused by another test run, but not directly related to it. Looking at 019_replslot_limit.pl, I see ----- # freeze walsender and walreceiver. Slot will still be active, but walreceiver # won't get anything anymore. kill 'STOP', $senderpid, $receiverpid; $node_primary3->advance_wal(2); ----- This fragment seems to assume that the effect of the kill 'STOP' is instantaneous. If it's not, it seems possible that the walsender process could manage to push out the WAL data added by "advance_wal" before it gets frozen, in which case the subsequent loop that's watching for it to get killed would watch in vain, which matches your symptoms. As far as a quick grep finds, this is the only test we have that relies on kill 'STOP'. I suspect that it's too clever for its own good. I trawled the last three months' worth of buildfarm logs and didn't find any other matches to "not ok 19 - walsender termination logged". So this is a pretty improbable failure mode, whatever the explanation is. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Require sizeof(bool) == 1.
- 97525bc5c8ff 18.0 landed
-
If a C23 compiler is detected, try asking for C17.
- f4e8f137bfb0 10 (unreleased) landed
- 0c7171b32e64 9.2 (unreleased) landed
- 102be6634e6f 9.3 (unreleased) landed
- b1b8b8e6f141 9.4 (unreleased) landed
- 5b40ce749c6f 9.5 (unreleased) landed
- 70cf253d18da 9.6 (unreleased) landed
- 170e416034ec 11 (unreleased) landed
- 3f302f0ed06f 12 (unreleased) landed
- 59ea17c43c6c 13.19 landed
- 1fd57e5bbf87 14.16 landed
- f00c401c65af 15.11 landed
-
Fix C23 compiler warning
- f7a929a007e6 16.7 landed
- f3834c12afd8 17.3 landed
-
Rename C23 keyword
- ae145d1de677 16.7 landed
- ad89c8bda1f0 17.3 landed
-
Assume that <stdbool.h> conforms to the C standard.
- bc5a4dfcf739 18.0 landed
- 0813a5e69186 17.3 landed
- 0f6d902308a8 16.7 landed
- 94817d9d94d0 15.11 landed
- e0874080c472 14.16 landed
- 13242b64e15d 13.19 landed
- 15a89e2cc501 12 (unreleased) landed
- 0305dd3adef2 11 (unreleased) landed
-
Revise tree-walk APIs to improve spec compliance & silence warnings.
- 1c27d16e6e5c 16.0 cited