| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Konstantin Izmailov <pgfizm(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Savepoint and prepared transactions |
| Date: | 2010-05-05 06:18:57 |
| Message-ID: | p2rdcc563d11005042318t356c476dua014b2141bb6291d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov <pgfizm(at)gmail(dot)com> wrote:
> Hi,
> I'm working on a solution that utilizes 2 phase commit protocol (between SQL
> Server and PostgreSQL). Normally PostgreSQL statements sequense is:
> 1. START
> 2. <inserts, updates, etc.>
> 3. PREPARE TRANSACTION 'uuid'
> 4. COMMIT PREPARED 'uuid'
>
> What if on step 2 user application issues statements with SAVEPOINTs, e.g.
> 2.1. SAVEPOINT svp1
> 2.2. <inserts, updates, etc.>
> 2.3. SAVEPOINT svp2
> 2.4. <inserts, updates, etc.>
> 2.5. RELEASE SAVEPOINT svp2
> 2.6. ROLLBACK TO SAVEPOINT svp1
> 2.7. <inserts, updates, etc.>
>
> Is this allowed and safe to use?
What are you expecting to happen?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amol Chiplunkar | 2010-05-05 06:19:06 | Re: Table alias and inherited tables |
| Previous Message | Gerd Koenig | 2010-05-05 06:05:46 | no such file euc2004... while initdb 9.0Beta |