| From: | Eugene Strulyov <eugene_s(dot)_at_(dot)corefa(dot)_dot_(dot)kill_all_spammers(at)corefa(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | transaction timeout |
| Date: | 2003-09-26 16:48:53 |
| Message-ID: | 200309261248.54002.EugeneStrulyov<eugene_s_at_corefa_dot_kill_all_spammers> |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi everybody,
Our aplpication uses PostgreSQL for data store. We have a problem with the way
long-running transactions are handled.
Our application had a bug (from what I understand it went into an infinite
loop). As a result, the transaction it was processing was neither committed
nor rolled back. Because of that, the misbehaving process was left holding
the locks and none of the other processes were able to do transactions.
My question is, how do I get PostgreSQL to automatically abort transactions
that take longer than a certain timeout?
thanks in advance,
Eugene
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-09-26 17:01:44 | Re: About GPL and proprietary software |
| Previous Message | Dennis Gearon | 2003-09-26 16:11:08 | Re: Good way to insert/update when you're not sure of duplicates? |