"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
In response to
pgsql-interfaces by date
|Next:||From: Keary Suska||Date: 2006-03-29 16:55:28|
|Subject: Libpq and PGConn|
|Previous:||From: Vivek Khera||Date: 2006-03-22 16:46:38|
|Subject: Re: db sever seems to be dropping connections |
pgsql-general by date
|Next:||From: Tom Lane||Date: 2006-03-22 17:46:49|
|Subject: Re: How to release locks |
|Previous:||From: Thomas F. O'Connell||Date: 2006-03-22 17:10:20|
|Subject: Re: Autovacuum Daemon Disrupting dropdb?|