From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Rushabh Doshi" <rdoshi(at)vmware(dot)com> |
Cc: | "Chris" <dmagick(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: db sever seems to be dropping connections |
Date: | 2006-03-22 17:21:03 |
Message-ID: | 17644.1143048063@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-interfaces |
"Rushabh Doshi" <rdoshi(at)vmware(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-22 17:46:49 | Re: How to release locks |
Previous Message | Thomas F. O'Connell | 2006-03-22 17:10:20 | Re: Autovacuum Daemon Disrupting dropdb? |
From | Date | Subject | |
---|---|---|---|
Next Message | Keary Suska | 2006-03-29 16:55:28 | Libpq and PGConn |
Previous Message | Vivek Khera | 2006-03-22 16:46:38 | Re: db sever seems to be dropping connections |