pgsql: Fix canAcceptConnections() bugs introduced by replication-relate - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix canAcceptConnections() bugs introduced by replication-relate
Date
Msg-id E1PHjeT-0005fS-6f@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix canAcceptConnections() bugs introduced by replication-related patches.

We must not return any "okay to proceed" result code without having checked
for too many children, else we might fail later on when trying to add the
new child to one of the per-child state arrays.  It's not clear whether
this oversight explains Stefan Kaltenbrunner's recent report, but it could
certainly produce a similar symptom.

Back-patch to 8.4; the logic was not broken before that.

Branch
------
REL8_4_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6318fa0fdb1ad22b489f1f9f8018ffa70e2e724c

Modified Files
--------------
src/backend/postmaster/postmaster.c |   29 +++++++++++++++++------------
1 files changed, 17 insertions(+), 12 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Work around make 3.80 bug with long expansions of $(eval).
Next
From: Tom Lane
Date:
Subject: pgsql: Fix canAcceptConnections() bugs introduced by replication-relate