Re: Psycopg 2.2.x issue with PgBouncer
Federico Di Gregorio <fog-NGVKUo/i/[email protected]> Tue, 17 Aug 2010 09:17:07 +0200
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============8544442799965026982== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9ED5C3FBE954DD51695C7C4D" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9ED5C3FBE954DD51695C7C4D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 04/08/2010 13:20, Daniele Varrazzo wrote: > 2010/8/4 Devrim G=C3=9CND=C3=9CZ <[email protected]>: >> > >> > 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? > If you ensure to have a commit/rollback before close/GC of the > connection, PgBouncer should work fine with all the psycopg versions. > If you can make this change and run the program with the current 2.2.2 > a feedback would be very appreciated. >=20 > I haven't heard from fog if he prefers to have 2.2.3 reproducing the > behavior of pre 2.2, where a rollback was automatically issued on > close(), or if drop it for the reasons discussed in this thread. Hi *, before going on vacancy I didn't do the release because there was a discussion going on. From what I read it seems to me that rolling back the changes on master and documenting the behaviour is the best way to fix that. Right? federico --=20 Federico Di Gregorio fog-NGVKUo/i/[email protected] Questa lista non pretende di essere il riferimento torinese per il software libero o altre cazzate del genere. -- Silvano, su torte --------------enig9ED5C3FBE954DD51695C7C4D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxqN3sACgkQvcCgrgZGjesDGACeIGbK1OVPAKSZ20WOYEDYsOjk U0cAnRkgDXynkVdAqLbf/Et+sh13rBf3 =WEIe -----END PGP SIGNATURE----- --------------enig9ED5C3FBE954DD51695C7C4D-- --===============8544442799965026982== 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 --===============8544442799965026982==--