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 B9C439FA219; Tue, 20 Jun 2006 10:52:50 -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 39219-06-2; Tue, 20 Jun 2006 10:52:44 -0300 (ADT) X-Greylist: delayed 00:19:22.334095 by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 6F4229FA64B; Tue, 20 Jun 2006 10:52:40 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from rhws.home.edu (66-23-211-34.clients.speedfactory.net [66.23.211.34]) by svr4.postgresql.org (Postfix) with ESMTP id EFB9F5AF047; Tue, 20 Jun 2006 13:33:16 +0000 (GMT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by rhws.home.edu (8.13.1/8.13.1) with ESMTP id k5KDXD8t002862; Tue, 20 Jun 2006 09:33:13 -0400 Message-ID: <4497F919.7050203@3times25.net> Date: Tue, 20 Jun 2006 09:33:13 -0400 From: Geoffrey User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org Subject: help with error message from perl Pg Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/794 X-Sequence-Number: 97166 We have an unusual problem with some perl code that is processing data via DBD facility. Basically, the code consists of various subroutines that are identified in a hash. The primary script then references the subroutines through a &$prog(...) syntax. What appears to happen is that all subroutines will run just fine if they do not need to do any deletes or updates to the database. Any subroutine that does a delete or update runs fine, but the subsequent routine fails with the following error: prgcaphlg: FATAL: invalid frontend message type 78 server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. Searching google for 'invalid frontend message type 78' returns no hits, which is a scary thing. Any insights would be greatly appreciated. -- Until later, Geoffrey Any society that would give up a little liberty to gain a little security will deserve neither and lose both. - Benjamin Franklin