Re: transaction timeout

On Tue, 2005-07-26 at 11:24, Dr NoName wrote:
> > The common view on this kind of thing is that if
> > your client is broken,
> > you need to fix it.
>
> The problem is, we can't fix the users, nor can we fix
> other software that our client has to interact with.
> There will always be occasional situations when a
> client gets stuck.

> > That said, I have seen some folks post about writing
> > a perl or shell
> > script that runs every x minutes looking for
> > connections that have been
> > idle for > a certain amount of time and kill the
> > backend associated with
> > it (sigterm, not -9...)
>
> what are the implications of killing a postmaster
> process?

A Sigterm is generally considered safe. It's -9 and its ilk that you
need to be wary of.

I think we and you both need more information about this failure. Do
you have any logging turned on that could give us a clue to what's
causing this failure?

It sounds to me more like one of the user apps is DOSing the server with
large unconstrained joins or something similarly dangerous to do.