Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] db sever seems to be dropping connections
- 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: [GENERAL] db sever seems to be dropping connections
- Date: Wed, 22 Mar 2006 12:21:03 -0500
- Message-id: <17644.1143048063@sss.pgh.pa.us> <text/plain>
"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
- Prev by Date: Re: using libpq with the free Borland compiler or DEV-cpp
- Next by Date: Libpq and PGConn
- Previous by thread: using libpq with the free Borland compiler or DEV-cpp
- Next by thread: Libpq and PGConn
- Indexes: