Re: Checkpoints stuck after a failed bulk write inside a savepoint

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Joao Rito <joaovictor(dot)rito(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Checkpoints stuck after a failed bulk write inside a savepoint
Date: 2026-11-20 22:34:36
Message-ID: awDK_IaNR1dRHXd_@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 20, 2026 at 05:00:49PM +0900, Michael Paquier wrote:
> On Fri, Nov 20, 2026 at 04:40:53PM +0900, Michael Paquier wrote:
>> That's still not better than what's on HEAD, but it reduces the window
>> of the useless syncs to be close to zero in practice, only when a
>> checkpoint had the idea to run between the smgrregistersync() and the
>> smgrregistersync() calls. And we don't lose track of the flag value
>> due to the fact that we don't use it.
>
> Ahem.. between the smgrregistersync() and the smgrimmedsync() calls.
> Bad copy-paste.

Please find attached to show the idea. I have not spent much time
testing it. (Note that the CI has failed once on Windows, not sure if
this was related to this patch or not.)
--
Michael

Attachment Content-Type Size
v2-0001-Avoid-DELAY_CHKPT_START-in-smgr_bulk_finish.patch text/plain 2.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message T, Adesh 2026-11-20 22:46:07 Postmaster PANIC on a standby with slot synchronization enabled
Previous Message surya poondla 2026-11-20 21:30:04 Re: Stop masking visibility information during WAL consistency checking