Re: Be strict when request to flush past end of WAL in WaitXLogInsertionsToFinish

From: surya poondla <suryapoondla4(at)gmail(dot)com>
To: Paul Kim <mok03127(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, bharath(dot)rupireddyforpostgres(at)gmail(dot)com
Subject: Re: Be strict when request to flush past end of WAL in WaitXLogInsertionsToFinish
Date: 2026-11-02 19:44:50
Message-ID: CAOVWO5rXewo2wodq1jBrg6BxbkDVuwKmZnGogZ2B90sWheacGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Paul,

Thank you for the v8. It addresses my previous points.

v8 applies cleanly on master (5681f0cfa5a) and builds without
warnings with assertions enabled. 039_end_of_wal.pl passes (17/17),
including the two new checks, and the server log shows no "request to
flush past end of generated WAL" message and no assertion failure.

v8 looks good to me.

Regards,
Surya Poondla

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-11-02 19:46:56 Re: ZSTD TOAST compression, and an extensible compression method encoding
Previous Message Masahiko Sawada 2026-11-02 19:44:45 Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation