| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | postgres(at)jeltef(dot)nl |
| Cc: | jacob(dot)champion(at)enterprisedb(dot)com, tomas(at)vondra(dot)me, zsolt(dot)parragi(at)percona(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, davecramer(at)gmail(dot)com, hlinnaka(at)iki(dot)fi |
| Subject: | Re: Add GoAway protocol message for graceful but fast server shutdown/switchover |
| Date: | 2026-03-25 00:36:20 |
| Message-ID: | 20260325.093620.1348358766802101218.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Reading the proposal, I have some questions. Sorry if they have been
already discussed.
1. If clients do not disconnect a session even if they have received
the GoAway message, PostgreSQL server will give up the shutdown
sequence. In this case, shouldn't the PostgreSQL server send a
message indicating "I have given up the smart shutdown request"?
Otherwise, the fact that GoAway has been received will remain in
the client, and if the client does not check the receiving timely,
the client may exit the session unnecessarily.
2. Can we use a NOTICE message instead of the new protocol GoAway for
the purpose? Frontends are expected to receive and handle NOTICE
messages while processing frontend/backend protocol. So I think it
is fair to expect clients to find the NOTICE message and behave as
we discussed. This way, we don't need the GoAway message.
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2026-03-25 00:39:07 | Re: raise ERROR between EndPrepare and PostPrepare_Locks causes ROLLBACK 2pc PAINC |
| Previous Message | David Rowley | 2026-03-25 00:31:30 | Re: Fix "could not find memoization table entry" |