Re: BUG #17928: Standby fails to decode WAL on termination of primary

Noah Misch <noah@leadboat.com>

From: Noah Misch <noah@leadboat.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Alexander Lakhin <exclusion@gmail.com>, Sergei Kornilov <sk@zsrv.org>, Tom Lane <tgl@sss.pgh.pa.us>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, pgsql-bugs@lists.postgresql.org, Fujii Masao <masao.fujii@oss.nttdata.com>, pgbf@twiska.com
Date: 2023-09-25T01:32:44Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Correct assertion and comments about XLogRecordMaxSize.

  2. Fix edge-case for xl_tot_len broken by bae868ca.

  3. Don't use Perl pack('Q') in 039_end_of_wal.pl.

  4. Don't trust unvalidated xl_tot_len.

  5. Make recovery report error message when invalid page header is found.

  6. Add more protections in WAL record APIs against overflows

On Mon, Sep 25, 2023 at 01:18:56PM +1300, Thomas Munro wrote:
> On Mon, Sep 25, 2023 at 12:58 PM Michael Paquier <michael@paquier.xyz> wrote:
> > On Mon, Sep 25, 2023 at 09:02:35AM +1300, Thomas Munro wrote:
> > > I see there was a failure on 16 on the very slow AIX box, and I have
> > > access so looking into that...
> >
> > Lucky you, if I may say ;)
> 
> FTR anyone involved with an open source project can get an account on
> the GCC compile farm machines.  That particular machine is so
> overloaded that it's practically unusable (~8 hours to run the test,
> hard to run vi etc).

topminnow (gcc23) and frogfish (gcc22) are also part of the compile farm.
They're faster than sungazer (gcc111) for src/test/recovery.