After takin a swig o' Arrakan spice grog, adnandursun@asrinbilisim.com.tr belched out:
> On Sun, 1 May 2005 14:35:37 -0500
> Bruno Wolff III <bruno@wolff.to> wrote:
>>On Sun, May 01, 2005 at 19:57:37 +0300,
>> adnandursun@asrinbilisim.com.tr wrote:
>>>
>>> Listen Tom, write a client software that releases the
>>> resources / locks that was hold before client power is
>>down
>>> or client connection was lost.
>>
>>If Postgres can tell the connection has been lost then it
>>should roll back the connection.
>
> Yes, but, Can PostgreSQL know which connection is lost or
> live or dead ?
Certainly, with the "magic connection analysis protocol."
Or not...
In order to that sort of analysis, you need to have some form of
heartbeat monitor on the connection, thereby requiring extra
connections.
It could make sense to attach that kind of extra apparatus to a
connection pool manager like pgpool, but probably not directly to
PostgreSQL itself.
You might want to look into pgpool; that is something that many people
interested in "enterprise usage" of PostgreSQL are looking into...
--
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/slony.html
"A army's effectiveness depends on its size, training, experience and
morale, and morale is worth more than all the other factors combined."
-- Napoleon Bonaparte
