Re: Safely Killing Backends (Was: Applications that leak connections) - Mailing list pgsql-general

From Jim Wilson
Subject Re: Safely Killing Backends (Was: Applications that leak connections)
Date
Msg-id 200502050141.j151fthS021924@linus.kelco1.com
Whole thread Raw
In response to Safely Killing Backends (Was: Applications that leak connections)  (Thomas F.O'Connell <tfo@sitening.com>)
List pgsql-general
> On Fri, Feb 04, 2005 at 05:01:43PM -0500, Jim Wilson wrote:
>
> > Rather than getting into the raised eyebrow thing , I\\\\\\\'d
suggest
> > checking your "qualifiers". Consider that with Postgres, if killing
a
> > single connection brings the whole server down, you will loose
_all_
> > uncommitted data. If you did not, then I would call that a bug. The
> > weakness is not in the data integrity (directly), it is in the
> > integrity of the server processes and their managability.
>
> Are you saying that your applications regularly leave uncommitted
> transactions for long periods of time?  That sounds like bugs in your
> applications to me.
>

I never said that.

<snip>
>
> What\'s with the backslashes anyway?
>

Well, I\'m beta testing an email client.  Good question! :-)

Best,

Jim Wilson



pgsql-general by date:

Previous
From: Jim Wilson
Date:
Subject: Re: Safely Killing Backends (Was: Applications that leak connections)
Next
From: "Juan Casero (FL FLC)"
Date:
Subject: Re: plpgsql function errors