| From: | Jim Wilson <jimw(at)kelcomaine(dot)com> |
|---|---|
| To: | alvherre(at)dcc(dot)uchile(dot)cl, jimw(at)kelcomaine(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Safely Killing Backends (Was: Applications that leak connections) |
| Date: | 2005-02-05 01:41:55 |
| Message-ID: | 200502050141.j151fthS021924@linus.kelco1.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Casero (FL FLC) | 2005-02-05 03:03:34 | Re: plpgsql function errors |
| Previous Message | Jim Wilson | 2005-02-05 01:34:39 | Re: Safely Killing Backends (Was: Applications that leak connections) |