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
------
REL9_0_STABLE
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=c350b01e2f72249ce6bcb642e0ee6730838b0cfe
Modified Files
--------------
src/backend/postmaster/postmaster.c | 33 +++++++++++++++++++--------------
1 files changed, 19 insertions(+), 14 deletions(-)