From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, elein <elein(at)varlena(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Adding MERGE to the TODO list (resend with subject) |
Date: | 2004-05-09 04:13:31 |
Message-ID: | 409DAFEB.7020300@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-sql |
> I intend to release locks on subtransaction abort, so if the update
> fails there's room for another transaction to insert the key (which I
> understand should fail?). I guess there's a different locking mechanism
> needed; I believe nested transactions will not be enough.
Except you can keep trying and trying without the outermost transaction
failing.
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-05-09 05:18:25 | Re: Adding MERGE to the TODO list (resend with subject) |
Previous Message | Alvaro Herrera | 2004-05-09 03:54:05 | Re: Adding MERGE to the TODO list (resend with subject) |
From | Date | Subject | |
---|---|---|---|
Next Message | Shachar Shemesh | 2004-05-09 04:34:31 | Re: Relocatable installs |
Previous Message | Alvaro Herrera | 2004-05-09 03:54:05 | Re: Adding MERGE to the TODO list (resend with subject) |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-05-09 05:18:25 | Re: Adding MERGE to the TODO list (resend with subject) |
Previous Message | Alvaro Herrera | 2004-05-09 03:54:05 | Re: Adding MERGE to the TODO list (resend with subject) |