Re: Add GoAway protocol message for graceful but fast server shutdown/switchover - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Add GoAway protocol message for graceful but fast server shutdown/switchover
Date
Msg-id DFJ3E1X9169E.WV892I950LYW@jeltef.nl
Whole thread Raw
In response to Add GoAway protocol message for graceful but fast server shutdown/switchover  ("Jelte Fennema-Nio" <me@jeltef.nl>)
List pgsql-hackers
On Thu Oct 23, 2025 at 3:04 PM CEST, Jelte Fennema-Nio wrote:
> This change introduces a new GoAway backend-to-frontend protocol
> message (byte 'g') that the server can send to the client to politely
> request that client to disconnect/reconnect when convenient.

After pushback on another threadabout introducing additional minor
protocol versions[1], I've decided to change this patch to use a
protocol extension instead of a minor version bump.

I personally don't think this patch is any better now, but that's fine.
If this means it has a chance of going into PG19, that's totally worth
it to me. (also I'd like to stop spending time on discussions where
clearly neither side will agree with eachother).

The automated test requires the not yet committed pytest changes[2]. I
don't think the automated test is required for a merge, so I don't think
this is blocked on pytest support getting in. It's here mainly as an
example and as a regression test during development, to know I did not
break the goaway functionality while changing the implementation.

[1]: https://www.postgresql.org/message-id/flat/CADK3HHKe1PA1U6aB5-7tWBQ0yZGgNvY7H=ECDD9955Pas_zx_Q@mail.gmail.com
[2]: https://commitfest.postgresql.org/patch/6045/

Attachment

pgsql-hackers by date:

Previous
From: Neil Chen
Date:
Subject: Re: Optimize SnapBuildPurgeOlderTxn: use in-place compaction instead of temporary array
Next
From: shveta malik
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication