Re: Safely Killing Backends (Was: Applications that leak connections)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Wilson <jimw(at)kelcomaine(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Safely Killing Backends (Was: Applications that leak connections)
Date: 2005-02-04 21:35:11
Message-ID: 17559.1107552911@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jim Wilson <jimw(at)kelcomaine(dot)com> writes:
> If you are not very careful about how you handle orphaned connections
> in Postgres you will likely lose data....not "maybe" like a long
> shot...but "likely".

[ raised eyebrow ... ] Say again? I don't know of any reason why a
lost connection would cause loss of (successfully committed) transactions.
Not even if a DBA with an itchy "kill -9" trigger finger is in charge of
cleaning up the lost connections. Please describe the scenarios you've
had problems with.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-02-04 21:49:08 Re: plpgsql function errors
Previous Message Jim Wilson 2005-02-04 20:58:33 Re: Safely Killing Backends (Was: Applications that leak connections)