<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<p>Sorry,</p>
<p>this this time I dont understand you. We have no any problems with the parameter<span style="font-size: 12pt;"> </span><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">child_max_connections!</span></p>
<p><br>
</p>
<p>My email was regarding the current problem #271. I want to say that in the latest patch we still could reproduce the the problem. And I sent you self contained test - extended modified test.</p>
<p>It seems we misunderstand each other )</p>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Tatsuo Ishii <ishii@sraoss.co.jp><br>
<b>Sent:</b> Wednesday, March 15, 2017 2:10 AM<br>
<b>To:</b> Sergey Kim<br>
<b>Cc:</b> pgpool-hackers@pgpool.net; Boris Voskanov<br>
<b>Subject:</b> Re: [pgpool-committers: 3836] pgpool: Branch refs/heads/bug271 was created</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">> Yes, this value is in place.<br>
> <br>
> But does it make sense when comes to the being resolved issue?<br>
<br>
Sorry, I don't understand you. This behavior regarding<br>
child_max_connections has not been changed since at least 3.4.<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" id="LPlnk192953" previewremoved="true">
http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:http://www.sraoss.co.jp<br>
<br>
> ________________________________<br>
> From: Tatsuo Ishii <ishii@sraoss.co.jp><br>
> Sent: Wednesday, March 15, 2017 1:40:21 AM<br>
> To: Sergey Kim<br>
> Cc: pgpool-hackers@pgpool.net; Boris Voskanov<br>
> Subject: Re: [pgpool-committers: 3836] pgpool: Branch refs/heads/bug271 was created<br>
> <br>
> Do you set child_max_connections to 1? At least the log said so. A<br>
> Pgpool-II child process exited because of this, i.e. it seems to be a<br>
> normal behavior.<br>
> <br>
>> 2017-03-14T16:06:37.894944+03:00 OAA-54999c4d7735 pgpool[25595]: [93-1] 2017-03-14 16:06:37: pid 25595:LOG: child exiting, 1 connections reached<br>
>> 2017-03-14T16:06:37.895079+03:00 OAA-54999c4d7735 pgpool[25595]: [93-2] 2017-03-14 16:06:37: pid 25595:LOCATION: child.c:406<br>
> <br>
> Best regards,<br>
> --<br>
> Tatsuo Ishii<br>
> SRA OSS, Inc. Japan<br>
> English: <a href="http://www.sraoss.co.jp/index_en.php" id="LPlnk628338" previewremoved="true">
http://www.sraoss.co.jp/index_en.php</a><br>
> Japanese:http://www.sraoss.co.jp<br>
> <br>
>> Tatsuo,<br>
>><br>
>><br>
>> this time all previously created tests succeeded but out application failed to start. So we started searching for the problem and could reproduce "balanced select problem". The test can run for minutes before reproduction of the problem (((<br>
>><br>
>> I'm not sure if it can help but please pay attention that time lag between insert is select requests is very small.<br>
>><br>
>><br>
>> Please see the pgpool logs:<br>
>><br>
>> 2017-03-14T16:06:37.889485+03:00 OAA-54999c4d7735 pgpool[25595]: [79-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: B message<br>
>> 2017-03-14T16:06:37.889702+03:00 OAA-54999c4d7735 pgpool[25595]: [79-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.889924+03:00 OAA-54999c4d7735 pgpool[25595]: [80-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: B message<br>
>> 2017-03-14T16:06:37.890090+03:00 OAA-54999c4d7735 pgpool[25595]: [80-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.890248+03:00 OAA-54999c4d7735 pgpool[25595]: [81-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: Execute: BEGIN<br>
>> 2017-03-14T16:06:37.890378+03:00 OAA-54999c4d7735 pgpool[25595]: [81-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.890535+03:00 OAA-54999c4d7735 pgpool[25595]: [82-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: Execute: BEGIN<br>
>> 2017-03-14T16:06:37.890693+03:00 OAA-54999c4d7735 pgpool[25595]: [82-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.890863+03:00 OAA-54999c4d7735 pgpool[25595]: [83-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: Parse: insert into write_table(id) values($1)<br>
>> 2017-03-14T16:06:37.891144+03:00 OAA-54999c4d7735 pgpool[25595]: [83-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.891390+03:00 OAA-54999c4d7735 pgpool[25595]: [84-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: B message<br>
>> 2017-03-14T16:06:37.891637+03:00 OAA-54999c4d7735 pgpool[25595]: [84-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.891895+03:00 OAA-54999c4d7735 pgpool[25595]: [85-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: D message<br>
>> 2017-03-14T16:06:37.892091+03:00 OAA-54999c4d7735 pgpool[25595]: [85-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.892272+03:00 OAA-54999c4d7735 pgpool[25595]: [86-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: Execute: insert into write_table(id) values($1)<br>
>> 2017-03-14T16:06:37.892442+03:00 OAA-54999c4d7735 pgpool[25595]: [86-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.892642+03:00 OAA-54999c4d7735 pgpool[25595]: [87-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: B message<br>
>> 2017-03-14T16:06:37.892828+03:00 OAA-54999c4d7735 pgpool[25595]: [87-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.892998+03:00 OAA-54999c4d7735 pgpool[25595]: [88-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: Execute: select id from write_table where id = $1<br>
>> 2017-03-14T16:06:37.893187+03:00 OAA-54999c4d7735 pgpool[25595]: [88-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.893359+03:00 OAA-54999c4d7735 pgpool[25595]: [89-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: ABORT<br>
>> 2017-03-14T16:06:37.893584+03:00 OAA-54999c4d7735 pgpool[25595]: [89-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.893839+03:00 OAA-54999c4d7735 pgpool[25595]: [90-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: ABORT<br>
>> 2017-03-14T16:06:37.894039+03:00 OAA-54999c4d7735 pgpool[25595]: [90-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.894220+03:00 OAA-54999c4d7735 pgpool[25595]: [91-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 0 backend pid: 25885 statement: DISCARD ALL<br>
>> 2017-03-14T16:06:37.894403+03:00 OAA-54999c4d7735 pgpool[25595]: [91-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.894587+03:00 OAA-54999c4d7735 pgpool[25595]: [92-1] 2017-03-14 16:06:37: pid 25595:LOG: DB node id: 1 backend pid: 27691 statement: DISCARD ALL<br>
>> 2017-03-14T16:06:37.894753+03:00 OAA-54999c4d7735 pgpool[25595]: [92-2] 2017-03-14 16:06:37: pid 25595:LOCATION: pool_proto_modules.c:3208<br>
>> 2017-03-14T16:06:37.894944+03:00 OAA-54999c4d7735 pgpool[25595]: [93-1] 2017-03-14 16:06:37: pid 25595:LOG: child exiting, 1 connections reached<br>
>> 2017-03-14T16:06:37.895079+03:00 OAA-54999c4d7735 pgpool[25595]: [93-2] 2017-03-14 16:06:37: pid 25595:LOCATION: child.c:406<br>
>> 2017-03-14T16:06:37.895371+03:00 OAA-54999c4d7735 pgpool[25566]: [47-1] 2017-03-14 16:06:37: pid 25566:LOG: child process with pid: 25595 exits with status 256<br>
>> 2017-03-14T16:06:37.895635+03:00 OAA-54999c4d7735 pgpool[25566]: [47-2] 2017-03-14 16:06:37: pid 25566:LOCATION: pgpool_main.c:2380<br>
>> 2017-03-14T16:06:37.895943+03:00 OAA-54999c4d7735 pgpool[25566]: [48-1] 2017-03-14 16:06:37: pid 25566:LOG: fork a new child process with pid: 25887<br>
>> 2017-03-14T16:06:37.896174+03:00 OAA-54999c4d7735 pgpool[25566]: [48-2] 2017-03-14 16:06:37: pid 25566:LOCATION: pgpool_main.c:2466<br>
>><br>
>><br>
>><br>
>> And java client logs:<br>
>> 16:06:37.890 (2) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@689604d9, maxRows=0, fetchSize=0, flags=1<br>
>> 16:06:37.890 (2) FE=> Parse(stmt=null,query="BEGIN",oids={})<br>
>> 16:06:37.890 (2) FE=> Bind(stmt=null,portal=null)<br>
>> 16:06:37.890 (2) FE=> Execute(portal=null,limit=0)<br>
>> 16:06:37.890 (2) FE=> Parse(stmt=null,query="insert into write_table(id) values($1)",oids={23})<br>
>> 16:06:37.890 (2) FE=> Bind(stmt=null,portal=null,$1=<-613120604>)<br>
>> 16:06:37.890 (2) FE=> Describe(portal=null)<br>
>> 16:06:37.890 (2) FE=> Execute(portal=null,limit=0)<br>
>> 16:06:37.890 (2) FE=> Sync<br>
>> 16:06:37.892 (2) <=BE ParseComplete [null]<br>
>> 16:06:37.892 (2) <=BE BindComplete [unnamed]<br>
>> 16:06:37.892 (2) <=BE CommandStatus(BEGIN)<br>
>> 16:06:37.892 (2) <=BE ParseComplete [null]<br>
>> 16:06:37.892 (2) <=BE BindComplete [unnamed]<br>
>> 16:06:37.892 (2) <=BE NoData<br>
>> 16:06:37.892 (2) <=BE CommandStatus(INSERT 0 1)<br>
>> 16:06:37.893 (2) <=BE ReadyForQuery(T)<br>
>> 16:06:37.893 (2) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@18078bef, maxRows=0, fetchSize=0, flags=0<br>
>> 16:06:37.893 (2) FE=> Bind(stmt=S_1,portal=null,$1=<-613120604>)<br>
>> 16:06:37.893 (2) FE=> Execute(portal=null,limit=0)<br>
>> 16:06:37.893 (2) FE=> Sync<br>
>> 16:06:37.895 (2) <=BE BindComplete [unnamed]<br>
>> 16:06:37.895 (2) <=BE CommandStatus(SELECT 0)<br>
>> 16:06:37.895 (2) <=BE ReadyForQuery(T)<br>
>> 16:06:37.895 (2) FE=> Terminate<br>
>> Exception in thread "main" java.lang.RuntimeException: Balanced<br>
>> at com.pgpool.tests.Issue271_SingleThread.runTest(Issue271_SingleThread.java:57)<br>
>> at com.pgpool.tests.TestStarter.main(TestStarter.java:37)<br>
>><br>
>><br>
>> The java test is attached:<br>
>><br>
>> P/S:<br>
>> Pgpool was build from branch bug271:<br>
>> [root@OAA-54999c4d7735 pgpool2]# git log -2<br>
>> commit 0955a22fb7f30c5b9c1fabe2873c09246453ee50<br>
>> Author: Tatsuo Ishii <ishii@postgresql.org><br>
>> Date: Tue Mar 14 19:03:02 2017 +0900<br>
>><br>
>> Fix problem described in [pgpool-hackers: 2125].<br>
>><br>
>> Two problems are fixed:<br>
>><br>
>> - The writing_transaction flag is not reset at transaction<br>
>> committed/aborted. Before it was done in CommandComplete but now it<br>
>> is possible that we need to check the flag before a command complete<br>
>> message arrives. So at Execute, it is taken care by<br>
>> handle_query_context() which used to be a static function in<br>
>> CommandComplete.c. Also the session context memory is always cleared<br>
>> before start a session context.<br>
>><br>
>> - Ready for query Re-sync code path in read_kind_from_backend did not<br>
>> work. The pending message corresponding to the ready for query<br>
>> message could be a sync message, which does not have query<br>
>> context. But before we checked if there's a query context<br>
>> exists. The check is bogus and removed.<br>
>><br>
>> commit 7c955b2a2dfb77623055b5eae9afe041de3105ee<br>
>> Author: Tatsuo Ishii <ishii@postgresql.org><br>
>> Date: Sun Mar 12 10:19:34 2017 +0900<br>
>><br>
>> Downgrade 1 more ereport from LOG to DEBUG1.<br>
>><br>
>><br>
>><br>
>><br>
>> Sergey<br>
>> ________________________________<br>
>> From: Tatsuo Ishii <ishii@sraoss.co.jp><br>
>> Sent: Tuesday, March 14, 2017 1:28 PM<br>
>> To: Sergey Kim<br>
>> Cc: pgpool-hackers@pgpool.net<br>
>> Subject: Re: [pgpool-committers: 3836] pgpool: Branch refs/heads/bug271 was created<br>
>><br>
>> Hi Sergey,<br>
>><br>
>> I have created a new branch named "bug271" which has been used to<br>
>> develop the patch for bug 271 on private git repository. Now you could<br>
>> use either the email attached patches or the branch if it's<br>
>> convieninet for you. The branch was created against the master<br>
>> branch. I will occasionaly rebase it with the master branch. In the<br>
>> near future the branch will be merged into the master branch (and I<br>
>> plan to back-patch it to 3.6 stable tree).<br>
>><br>
>> Best regards,<br>
>> --<br>
>> Tatsuo Ishii<br>
>> SRA OSS, Inc. Japan<br>
>> English: <a href="http://www.sraoss.co.jp/index_en.php" id="LPlnk40712" previewremoved="true">
http://www.sraoss.co.jp/index_en.php</a><br>
>> Japanese:http://www.sraoss.co.jp<br>
>><br>
>> From: pgpool-committers-bounces@pgpool.net<br>
>> Subject: [pgpool-committers: 3836] pgpool: Branch refs/heads/bug271 was created<br>
>> Date: Tue, 14 Mar 2017 10:19:33 +0000<br>
>> Message-ID: <E1cnjYD-0005zz-GZ@gothos.postgresql.org><br>
>><br>
>>> Branch refs/heads/bug271 was created.<br>
>>><br>
>>> View: <a href="http://git.postgresql.org/gitweb?p=pgpool2.git;a=shortlog;h=refs/heads/bug271" id="LPlnk647828" previewremoved="true">
http://git.postgresql.org/gitweb?p=pgpool2.git;a=shortlog;h=refs/heads/bug271</a><br>
</div>
</span></font></div>
</div>
</body>
</html>