<span style=" font-size:10pt;font-family:sans-serif">Hello,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">thank you for
your answer.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">There should be
are enough connections available. The num_init_children is set to 300,
reserved_connections = 2.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Postgres offers
400 connections with 3 reserved connections.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">The application
which sends the statement opens 4 connections with 2 different combinations
user / application-names. So we have with 3 running the application
3 times we have at most 12 connections in use.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">We have played
with the different parameters for connections, max_pool, child_max_connections,
num_init_children and see no change. </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Authentication
is set to allow_clear_text_frontend_auth = 1 since we have over 1000
login roles in the database and user can change their password at any time.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">There are no specific
error messages in the Pgpool logfile. When Pgpool stalls we only see the
regular watchdog messages "WATCHDOG LOG: new IPC connection
received".</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
Regards, </span>
<br><span style=" font-size:10pt;font-family:sans-serif"> <br>
Ernst Hansmair<br>
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Von:
</span><span style=" font-size:9pt;font-family:sans-serif">pgpool-general-request@pgpool.net</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">An:
</span><span style=" font-size:9pt;font-family:sans-serif">pgpool-general@pgpool.net</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Datum:
</span><span style=" font-size:9pt;font-family:sans-serif">16.12.2021
05:54</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Betreff:
</span><span style=" font-size:9pt;font-family:sans-serif">pgpool-general
Digest, Vol 122, Issue 12</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Gesendet
von: </span><span style=" font-size:9pt;font-family:sans-serif">"pgpool-general"
<pgpool-general-bounces@pgpool.net></span>
<br>
<hr noshade>
<br>
<br>
<br><tt><span style=" font-size:10pt">Send pgpool-general mailing list
submissions to<br>
pgpool-general@pgpool.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span></tt><a href="https://www.pgpool.net/mailman/listinfo/pgpool-general"><tt><span style=" font-size:10pt">https://www.pgpool.net/mailman/listinfo/pgpool-general</span></tt></a><tt><span style=" font-size:10pt"><br>
or, via email, send a message with subject or body 'help' to<br>
pgpool-general-request@pgpool.net<br>
<br>
You can reach the person managing the list at<br>
pgpool-general-owner@pgpool.net<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of pgpool-general digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [pgpool-general: 7937] Pgpool does not accept new<br>
connections (ehansmair@prompt-software.de)<br>
2. [pgpool-general: 7938] Pgpool docker image md5<br>
authentification
issue (Nikolay Mastilo (HM))<br>
3. [pgpool-general: 7939] Re: Pgpool does not accept new<br>
connections (Tatsuo Ishii)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 15 Dec 2021 18:48:41 +0100<br>
From: ehansmair@prompt-software.de<br>
To: pgpool-general@pgpool.net<br>
Subject: [pgpool-general: 7937] Pgpool does not accept new<br>
connections<br>
Message-ID:<br>
<OF94B3674C.CA227CDC-ONC12587AC.005F7A13-C12587AC.0061D74E@prompt-software.de><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello,<br>
<br>
we have the problem, that Pgpool does not accept new connections when some
<br>
longer running SQLs are on their way.<br>
<br>
We are using Pgpool 4.2.5 till now only for automated fail over and online
<br>
recovery - connection pooling, load balancing, in memory query cache are
<br>
switched off. PostgreSQL streaming replication is used. <br>
<br>
We can provoke the effect with a SQL like<br>
<br>
select field_a, field_b, pg_sleep(120)<br>
from table_a<br>
where field_a = 12345 <br>
<br>
The statement simulates long running statements we are using.<br>
<br>
When we start the above statement 3 times or more with a delay of 1 second
<br>
Pgpool does not accept new connections for some minutes. We do not get
an <br>
error message or time out. Direct connections to Postgres are as fast as
<br>
always. <br>
<br>
The effect exists in a 2-node cluster and in a degenerated, single machine
<br>
cluster too. <br>
<br>
Any help is welcome.<br>
<br>
Sincerely Yours<br>
<br>
Ernst Hansmair<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <</span></tt><a href="http://www.pgpool.net/pipermail/pgpool-general/attachments/20211215/942bcda9/attachment-0001.htm"><tt><span style=" font-size:10pt">http://www.pgpool.net/pipermail/pgpool-general/attachments/20211215/942bcda9/attachment-0001.htm</span></tt></a><tt><span style=" font-size:10pt">><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 15 Dec 2021 22:00:54 +0200<br>
From: "Nikolay Mastilo (HM)" <nikm71@hotmail.com><br>
To: pgpool-general@pgpool.net<br>
Subject: [pgpool-general: 7938] Pgpool docker image md5<br>
authentification
issue<br>
Message-ID:<br>
<AM9P191MB127067AD787FC005D563F126C8769@AM9P191MB1270.EURP191.PROD.OUTLOOK.COM><br>
<br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hello All,<br>
<br>
Our Pgpool runs on Kubernetes and we use it most often as a load balancer.<br>
When the PostgreSQL connection was trusted without requiring a password,
<br>
everything was fine.<br>
<br>
Now we decided to connect to PG with password in md5 mode and got a <br>
problem with Pgpool. We receive messages like this:<br>
? "ERROR: Could not authenticate with backend using md5"<br>
? "Detail: no valid password found"<br>
<br>
Pgpool fails user authentication while we add an entry to the <br>
pool_passwd file with md5 username and password.<br>
This pool_passwd file contains only one user and password entry, which
I <br>
specify in the POSTGRES_USERNAME and POSTGRES_PASSWORD env variables.<br>
Pgpool runs in docker image pgpool / pgpool: 4.2.2 in k8s.<br>
<br>
Can anyone answer two questions, at least one:<br>
<br>
1.Is there any parameters or env variable in this docker image to enter
<br>
more than one user entry into the pool_passwd file in the docker image<br>
<br>
2. Is it possible to pass md5 authentication directly to PostgreSQL <br>
without checking the password on Pgpool.<br>
<br>
Help, please, the problem is very critical for us.<br>
<br>
We will be very grateful for any help or in the direction of where to <br>
move in deciding .<br>
<br>
Thanks in advance.<br>
<br>
<br>
-- <br>
Regards,<br>
Nikolay<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 16 Dec 2021 08:53:43 +0900 (JST)<br>
From: Tatsuo Ishii <ishii@sraoss.co.jp><br>
To: ehansmair@prompt-software.de<br>
Cc: pgpool-general@pgpool.net<br>
Subject: [pgpool-general: 7939] Re: Pgpool does not accept new<br>
connections<br>
Message-ID:<br>
<20211216.085343.665071583336796189.t-ishii@sranhm.sra.co.jp><br>
Content-Type: Text/Plain; charset=us-ascii<br>
<br>
> Hello,<br>
> <br>
> we have the problem, that Pgpool does not accept new connections when
some <br>
> longer running SQLs are on their way.<br>
> <br>
> We are using Pgpool 4.2.5 till now only for automated fail over and
online <br>
> recovery - connection pooling, load balancing, in memory query cache
are <br>
> switched off. PostgreSQL streaming replication is used. <br>
> <br>
> We can provoke the effect with a SQL like<br>
> <br>
> select field_a, field_b, pg_sleep(120)<br>
> from table_a<br>
> where field_a = 12345 <br>
> <br>
> The statement simulates long running statements we are using.<br>
> <br>
> When we start the above statement 3 times or more with a delay of
1 second <br>
> Pgpool does not accept new connections for some minutes. We
do not get an <br>
> error message or time out. Direct connections to Postgres are as fast
as <br>
> always. <br>
> <br>
> The effect exists in a 2-node cluster and in a degenerated, single
machine <br>
> cluster too. <br>
<br>
It is possible that all pgpool child process are busy. You can check<br>
by using pcp_proc_info command. Try:<br>
<br>
pcp_proc_info -p [port number specified by pcp_port] -h localhost -v -a|grep
Wait<br>
<br>
If you get no lines at all, then all pgpool child process are occupied<br>
by the long running queries. In this case you can:<br>
<br>
- increase num_init_children (requires restarting pgpool)<br>
<br>
- decrease the chance to issue the long running query.<br>
<br>
Best reagards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: </span></tt><a href=http://www.sraoss.co.jp/index_en.php><tt><span style=" font-size:10pt">http://www.sraoss.co.jp/index_en.php</span></tt></a><tt><span style=" font-size:10pt"><br>
Japanese:</span></tt><a href=http://www.sraoss.co.jp/><tt><span style=" font-size:10pt">http://www.sraoss.co.jp</span></tt></a><tt><span style=" font-size:10pt"><br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
pgpool-general mailing list<br>
pgpool-general@pgpool.net<br>
</span></tt><a href="http://www.pgpool.net/mailman/listinfo/pgpool-general"><tt><span style=" font-size:10pt">http://www.pgpool.net/mailman/listinfo/pgpool-general</span></tt></a><tt><span style=" font-size:10pt"><br>
<br>
<br>
------------------------------<br>
<br>
End of pgpool-general Digest, Vol 122, Issue 12<br>
***********************************************<br>
</span></tt>
<br>
<br>