Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record

From: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record
Date: 2026-02-26 10:35:57
Message-ID: CAO6_XqrwjxFZU=XDVaiRCygQYFSjSpwPqJUgWKfaNdw_fVa73Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

And here's a script reproducing the issue. It creates the clusters,
sets up the logical replication and runs the necessary query to leave
FPI_FOR_HINT as the last written record.

If successful, the script should have pg_stop stuck with 'waiting for
server to shut down.......', with the walsender stuck at 100% CPU.

Attachment Content-Type Size
reproduce_stuck_shutdown.sh text/x-sh 1.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-02-26 10:37:10 Re: Skipping schema changes in publication
Previous Message Jim Jones 2026-02-26 10:23:40 Re: Show comments in \dRp+, \dRs+, and \dX+ psql meta-commands