Re: Psycopg 2.2.x issue with PgBouncer

--===============5768547557015868026==
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-jJcA0cAyhNPt+RoVfu3C"


--=-jJcA0cAyhNPt+RoVfu3C
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Where are we on this? I will move to new servers next week with 2.2.X
series. I can rollback to 2.0.14, but I'd prefer to stick to 2.2.X
series. Was this fixes somewhere?


On Fri, 2010-07-23 at 16:45 -0700, Jason Yan wrote:
> I'm seeing an issue with how Psycopg 2.2.x handles connections with
> PgBouncer.  After a connection is closed, PgBouncer spits out the
> following:
>   2010-07-23 16:33:46.407 5282 LOG C-0x1e9ad80:
> test/[email protected]:33306 login successful: db=3Dtest user=3Dpostgres
>   2010-07-23 16:33:46.407 5282 LOG S-0x1eb8280:
> test/[email protected]:5432 new connection to server
>   2010-07-23 16:33:46.411 5282 LOG C-0x1e9ad80:
> test/[email protected]:33306 closing because: client close request
> (age=3D0)
>   2010-07-23 16:33:46.411 5282 LOG S-0x1eb8280:
> test/[email protected]:5432 closing because: unclean server (age=3D0)
>=20
> This kills PgBouncer's server backend which effectively kills
> connection pooling.  I've reproduced this behavior with both 2.2.1 and
> 2.2.2, but I've verified that 2.0.14 does not have this issue.  I'm
> running a clean build of PgBouncer 1.3.3 with the default
> configuration on Ubuntu 9.04 64-bit with the following PostgreSQL
> packages:
>   ii  postgresql                                 8.3.11-0ubuntu9.04
>                                object-relational SQL database
> (supported ve
>   ii  postgresql-8.3                             8.3.11-0ubuntu9.04
>                                object-relational SQL database, version
> 8.3
>   ii  postgresql-client-8.3                      8.3.11-0ubuntu9.04
>                                front-end programs for PostgreSQL 8.3
>   ii  postgresql-client-common                   97
>                                manager for multiple PostgreSQL client
> versi
>   ii  postgresql-common                          97
>                                PostgreSQL database-cluster manager
>   ii  postgresql-contrib-8.3                     8.3.11-0ubuntu9.04
>                                additional facilities for PostgreSQL
>=20
> And the small test script that I'm reproducing the issue with:
>   import psycopg2
>   connection =3D psycopg2.connect("dbname=3Dtest user=3Dpostgres
> host=3Dlocalhost port=3D6432")
>   cursor =3D connection.cursor()
>   cursor.execute("SELECT 1")
>   connection.close()
>=20
> Thanks,
> Jason
> _______________________________________________
> Psycopg mailing list
> Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
> http://lists.initd.org/mailman/listinfo/psycopg


--=20
Devrim G=C3=9CND=C3=9CZ
PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

--=-jJcA0cAyhNPt+RoVfu3C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkxZRYgACgkQtl86P3SPfQ7G1ACgh+JY/O9LLRnbrVHz+C7mv7sQ
FkMAoMNRSmPtsAJhcVpsxNT98i4An98X
=PDpx
-----END PGP SIGNATURE-----

--=-jJcA0cAyhNPt+RoVfu3C--


--===============5768547557015868026==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
http://lists.initd.org/mailman/listinfo/psycopg

--===============5768547557015868026==--