Re: Savepoint and prepared transactions - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Savepoint and prepared transactions
Date
Msg-id p2rdcc563d11005042318t356c476dua014b2141bb6291d@mail.gmail.com
Whole thread Raw
In response to Savepoint and prepared transactions  (Konstantin Izmailov <pgfizm@gmail.com>)
Responses Re: Savepoint and prepared transactions  (Konstantin Izmailov <pgfizm@gmail.com>)
List pgsql-general
On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov <pgfizm@gmail.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?

pgsql-general by date:

Previous
From: Konstantin Izmailov
Date:
Subject: Savepoint and prepared transactions
Next
From: Gerd Koenig
Date:
Subject: no such file euc2004... while initdb 9.0Beta