Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record
Date
Msg-id CAHGQGwGvnpN=2bo+F7H90YLFcx9=SazwLkcx+0gEcrbQy5NVZg@mail.gmail.com
Whole thread
In response to Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
Responses Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record
List pgsql-hackers
On Thu, Mar 5, 2026 at 5:40 PM Anthonin Bonnefoy
<anthonin.bonnefoy@datadoghq.com> wrote:
> So it was relying on GetInsertRecPtr() instead of
> GetXLogInsertRecPtr(). As mentioned in the thread, GetInsertRecPtr()
> only returns the position of the last full xlog page, meaning it
> doesn't fix the issue we have where the last partial page contains a
> continuation record.
>
> Testing the XLogFlush(GetInsertRecPtr()) patch with my script, I still
> get the shutdown stuck issue.
>
> Using GetXLogInsertRecPtr() is required to make sure the last partial
> page is correctly flushed.

Since GetXLogInsertRecPtr() returns a bogus LSN and XLogFlush() does
almost nothing during recovery, I added a !RecoveryInProgress() check
as follows. I've attached the latest version of the patch and updated
the commit message.

- if (got_STOPPING)
- XLogBackgroundFlush();
+ if (got_STOPPING && !RecoveryInProgress())
+ XLogFlush(GetXLogInsertRecPtr());

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: generating function default settings from pg_proc.dat
Next
From: "yonghao_lee@qq.com"
Date:
Subject: Re: [PATCH] Fix improper tuple deallocation in import_pg_statist()