| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| 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 10:43:08 |
| Message-ID: | dc7b844e0912300243m346b2883n2b6ecd38dcc0eba4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. Subsequent commands will be executed just fine
instead of being refused with the error message that the transaction
is already aborted... Right?
Joachim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tarun Sharma | 2009-12-30 10:45:25 | Re: Can we hide data from the superadmin |
| Previous Message | Kris Jurka | 2009-12-30 10:02:44 | Re: Cancelling idle in transaction state |