From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rushabh Doshi <rdoshi@vmware.com>
Cc: Chris <dmagick@gmail.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: db sever seems to be dropping connections
Date: Wed, 22 Mar 2006 12:21:03 -0500
Message-ID: <17644.1143048063@sss.pgh.pa.us> (raw)
In-Reply-To: <428B5EAB52D41B48BFE2D7D21C522D2B7C97EF@PA-EXCH01.vmware.com>
References: <428B5EAB52D41B48BFE2D7D21C522D2B7C97EF@PA-EXCH01.vmware.com>
"Rushabh Doshi" <rdoshi@vmware.com> writes:
> DBI handle: DBI::db=HASH(0x9480bdc) # this is the stale handle
> DBD::Pg::db disconnect failed: rollback failed at *** line 241.
> result of disconnect:
> disconnect failed for DBI::db=HASH(0x9480bdc): DBD::Pg::db disconnect
> failed: rollback failed at *** line 241.
This seems like fairly stupid programming within DBD::Pg --- there's no
reason for it to be issuing an explicit rollback command at disconnect,
as the backend will certainly do that itself on seeing the connection
drop. Possibly you could get the DBD::Pg developers to change that,
so that a disconnect would be more robust in the face of network failure
(and a tad faster too).
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, rdoshi@vmware.com, dmagick@gmail.com, pgsql-general@postgresql.org
Subject: Re: db sever seems to be dropping connections
In-Reply-To: <17644.1143048063@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox