X-Original-To: pgsql-general-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F21B09FA5F0; Tue, 20 Jun 2006 11:00:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 42196-01; Tue, 20 Jun 2006 10:59:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from svana.org (svana.org [125.62.94.225]) by postgresql.org (Postfix) with ESMTP id 58F769FA219; Tue, 20 Jun 2006 10:59:57 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 4.50) id 1Fsgld-0006t5-2Y; Tue, 20 Jun 2006 23:59:45 +1000 Date: Tue, 20 Jun 2006 15:59:45 +0200 From: Martijn van Oosterhout To: Geoffrey Cc: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: help with error message from perl Pg Message-ID: <20060620135945.GB25678@svana.org> Reply-To: Martijn van Oosterhout Mail-Followup-To: Geoffrey , pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org References: <4497F919.7050203@3times25.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Yylu36WmvOXNoKYn" Content-Disposition: inline In-Reply-To: <4497F919.7050203@3times25.net> X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kleptog@svana.org X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/796 X-Sequence-Number: 97168 --Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 20, 2006 at 09:33:13AM -0400, Geoffrey wrote: > We have an unusual problem with some perl code that is processing data=20 > via DBD facility. Basically, the code consists of various subroutines=20 > that are identified in a hash. The primary script then references the=20 > subroutines through a &$prog(...) syntax. What appears to happen is=20 > that all subroutines will run just fine if they do not need to do any=20 > deletes or updates to the database. Any subroutine that does a delete=20 > or update runs fine, but the subsequent routine fails with the following= =20 > error: >=20 > prgcaphlg: FATAL: invalid frontend message type 78 Errors in the FE-BE protocol are usually caused by users trying to use the same connection from multiple threads simultaneously. libpq doesn't handle that and so ends up sending things out of order. Are you using threads? Also, the database connection, how is the handle passed around? Youre not closing it accedently somewhere? Have a ncie day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to l= itigate. --Yylu36WmvOXNoKYn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEl/9QIB7bNG8LQkwRAlAEAJ99mbIN2mGnZjEmRGRtUKwKcTQpUQCZAa4G E/16Xd/9HzOPMJs2ZUe3BFk= =k0Ng -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn--