| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Manfred Koizar <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Static snapshot data |
| Date: | 2003-05-20 00:00:56 |
| Message-ID: | 24669.1053388856@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> But there are a lot of things to do before nested transactions become a
> reality. For example there is need to abort any transaction, including
> possible subtransactions, in the case of deadlock. How is this supposed
> to be? Do we abort the whole transaction tree? Do we abort only the
> branch of the tree that has the needed locks?
Deadlock is not different from any other elog(ERROR) condition: you
abort the innermost transaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-20 00:07:11 | Re: Text format protocol representation |
| Previous Message | Tony Reina | 2003-05-19 23:20:05 | Anyone have a Windows DLL of libpq? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-05-20 02:42:58 | Re: Heads up: 7.3.3 this Wednesday |
| Previous Message | Bruce Momjian | 2003-05-19 22:16:09 | Re: Cygwin PostgreSQL CVS Patch |