| From: | Dr NoName <spamacct11(at)yahoo(dot)com> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transaction timeout |
| Date: | 2005-07-26 16:24:51 |
| Message-ID: | 20050726162451.70502.qmail@web31501.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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?
thanks,
Eugene
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-07-26 16:39:08 | Re: transaction timeout |
| Previous Message | Dr NoName | 2005-07-26 16:19:10 | Re: transaction timeout |