sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-01 00:01:20 -04:00
Code Issues Projects Releases Wiki Activity

Don't send "cannot connect" errors on invalid startup packet

Browse Source 
Commit 16671ba6e7 moved the code that sends "sorry, too many clients
already" and other such messages, but it had the effect that we would
send that error even if the the startup packet processing failed, e.g.
because the client sent an invalid startup packet. That was not
intentional.

Spotted while reading the code again.
This commit is contained in:
Heikki Linnakangas 2023-12-30 22:18:54 +02:00
parent 4710b67d4d
commit 5632d6e18a
1 changed files with 34 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/backend/postmaster/postmaster.c
View File

@ -4354,6 +4354,8 @@ BackendInitialize(Port *port)
* now instead of wasting cycles on an authentication exchange. (This also
* allows a pg_ping utility to be written.)
*/
if (status == STATUS_OK)
{
switch (port->canAcceptConnections)
{
case CAC_STARTUP:
@ -4391,6 +4393,7 @@ BackendInitialize(Port *port)
case CAC_OK:
break;
}
}
/*
* Disable the timeout, and prevent SIGTERM again.