| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: BackendKeyData is mandatory? |
| Date: | 2025-06-19 07:06:47 |
| Message-ID: | 5715d5dc-c81e-4c53-bd72-c6964e9246e5@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17.06.25 03:10, Tatsuo Ishii wrote:
> My question is, BackendKeyData is mandatory or not. Currently
> Pgpool-II raises a fatal error if BackendKeyData is not sent before
> ReadyForQuery arrives. This is because without the message, frontend
> cannot send a CancelRequest message later on, as there's no secret
> key.
I think that's fine, if the server does not want to support query
cancellation. The current protocol description certainly does not
support the idea that it is a hard error *not* to send BackendKeyData.
It's also worth thinking about the new protocol 3.2 longer key data. A
paranoid server might choose to send key data only if protocol >=3.2 is
chosen and not if a lower, notionally less secure version is chosen.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-06-19 07:09:21 | Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx |
| Previous Message | Peter Eisentraut | 2025-06-19 07:00:25 | Re: minimum Meson version |