| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Joachim Wieland <joe(at)mcknight(dot)de> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, James Pye <lists(at)jwp(dot)name>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cancelling idle in transaction state |
| Date: | 2009-12-30 12:04:46 |
| Message-ID: | 1262174686.19367.5083.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-12-30 at 11:43 +0100, Joachim Wieland wrote:
> On Wed, Dec 30, 2009 at 12:28 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> >> I had to write an additional function AbortAnyTransaction() which
> >> aborts all transactions and subtransactions and leaves the transaction
> >> in the aborted state, is there an existing function to do this?
> >
> > AbortOutOfAnyTransaction()
>
> But this would clean up completely and not leave the transaction in
> the aborted state.
True
> Subsequent commands will be executed just fine
> instead of being refused with the error message that the transaction
> is already aborted...
True, but it is a subsequent transaction, not the same one. (I've
checked).
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-12-30 12:15:30 | Re: Cancelling idle in transaction state |
| Previous Message | Simon Riggs | 2009-12-30 11:41:28 | Re: Hot Standy introduced problem with query cancel behavior |