On Thursday 14 April 2005 21:08, Andrew Sullivan wrote: > On Thu, Apr 14, 2005 at 03:04:47PM -0400, Alvaro Herrera wrote: > > It is a Postgres limitation as well. We _could_ make the server "really > > start the transaction" at the point the first query is issued instead of > > when the BEGIN is issued. In fact this problem would go away if we did > > that. > > Yeah; I seem to remember Tom Lane suggesting such an approach at one > point. I had the vague idea it might happen in 8.0, but for some > reason I think it didn't. (Anyway, that's probably off topic for > this list.)
I don't see this behaviour under 8.0.0, and it's presumably fixed: http://archives.postgresql.org/pgsql-jdbc/2004-06/msg00018.php Is it safe to issue a "kill -2 <pid-of-idle-process>", will the connection-pool reconnect? -- Andreas Joseph Krogh <[EMAIL PROTECTED]> Senior Software Developer / Manager gpg public_key: http://dev.officenet.no/~andreak/public_key.asc ------------------------+---------------------------------------------+ OfficeNet AS | The most difficult thing in the world is to | Hoffsveien 17 | know how to do a thing and to watch | PO. Box 425 Skøyen | somebody else doing it wrong, without | 0213 Oslo | comment. | NORWAY | | Phone : +47 22 13 01 00 | | Direct: +47 22 13 10 03 | | Mobile: +47 909 56 963 | | ------------------------+---------------------------------------------+ ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend