[pgpool-hackers: 542] Re: PGPool 3.3.3 with Postgres 9.3.4 Bug

[sameer khan]

I dont have a straight answer, but have test it many time. If the node number of primary node is higher the sessions are not closing ( i am seeing). I will try to see the logs again, but i believe a bug a is there. 
Thanks



> Date: Wed, 4 Jun 2014 10:11:51 +0900
> To: khanzadap at hotmail.com
> CC: pgpool-hackers at pgpool.net
> Subject: Re: [pgpool-hackers: 538] PGPool 3.3.3 with Postgres 9.3.4 Bug
> From: ishii at postgresql.org
> 
> > Hi guys,
> > 
> > I have installed latest stable PG pool 3.3.3 complied from source with Postgresql 9.3.4. Following http://www.pgpool.net/pgpool-web/contrib_docs/simple_sr_setting2_3.3/index.html guide 100%. I am using the pgpool with django 1.6. everything runs fine on creating database, table and updates but when try to do unit testing with the django "django-discover-runner" the dropping of test databases fails with error that X number of session is connected.
> > 
> > After banging my head against it, i isolated the issue to Primary node and node number. If primary node number is below standby node number everything works well without any issue, but if the Primary node number is higher than standby node the test fails with X number of sessions connected with the database.
> > Please let me know if any one of you encountered such issue.
> 
> I'm not familiar with django. Do you know how to reproduce your issue
> by using more general tools, say psql?
> 
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20140604/8f38e275/attachment.html>