From e70376fe9d8becf6289565e87ab713ace74268a8 Mon Sep 17 00:00:00 2001 From: Tatsuo Ishii Date: Thu, 1 Aug 2019 15:45:21 +0900 Subject: [PATCH] Update 4.1 release note. --- doc/src/sgml/filelist.sgml | 1 + doc/src/sgml/release-4.1.sgml | 15 +++++++++------ doc/src/sgml/release.sgml | 1 + 3 files changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml index dc1e3cf47..81a923bce 100644 --- a/doc/src/sgml/filelist.sgml +++ b/doc/src/sgml/filelist.sgml @@ -182,6 +182,7 @@ + diff --git a/doc/src/sgml/release-4.1.sgml b/doc/src/sgml/release-4.1.sgml index f505f7ac2..93ad514f3 100644 --- a/doc/src/sgml/release-4.1.sgml +++ b/doc/src/sgml/release-4.1.sgml @@ -362,14 +362,17 @@ frontends and queues up more connection requests until one of child process becomes free. This mostly works well, but if each session - take long time, the queue grows long and the whole system + takes long time, the queue grows longer and the whole system does not work smoothly. To overcome the problem, a new way to deal with many connection requests from frontend is - implemented: just complain and refuse to connect to - Pgpool-II if number of - already exceeds. This - is exactly the same behavior - as PostgreSQL. + implemented: When + is set to 1 or greater, incoming connections from clients + are not accepted with error message "Sorry, too many clients + already", rather than blocked if the number of current + connections from clients is more than + (num_init_children - + reserved_connections). This is exactly + the same behavior as PostgreSQL. diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 11b2031d2..b8ef91565 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -72,6 +72,7 @@ For new features, add links to the documentation sections. subsets can easily be copied into back branches. --> +&release-4.1; &release-4.0; &release-3.7; &release-3.6; -- 2.39.5