Re: [GENERAL] Savepoint and prepared transactions

yep, thank you! On Wed, May 5, 2010 at 5:47 AM, Scott Marlowe wrote: > Should work. I'm not sure 2.5 release savepoint is necessary. > > On Wed, May 5, 2010 at 12:53 AM, Konstantin Izmailov > wrote: > > I expect that only changes on step 2.7 persisted in DB. > > > > On Tue, May 4, 2010 at 11:18

Re: [GENERAL] Savepoint and prepared transactions

Should work. I'm not sure 2.5 release savepoint is necessary. On Wed, May 5, 2010 at 12:53 AM, Konstantin Izmailov wrote: > I expect that only changes on step 2.7 persisted in DB. > > On Tue, May 4, 2010 at 11:18 PM, Scott Marlowe > wrote: >> >> On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmai

Re: [GENERAL] Savepoint and prepared transactions

I expect that only changes on step 2.7 persisted in DB. On Tue, May 4, 2010 at 11:18 PM, Scott Marlowe wrote: > On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov > wrote: > > Hi, > > I'm working on a solution that utilizes 2 phase commit protocol (between > SQL > > Server and PostgreSQL). No

Re: [GENERAL] Savepoint and prepared transactions

On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov 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. > 3. PREPARE TRANSACTION 'uuid' > 4. COMMIT PREPARED 'uuid' > > Wh

[GENERAL] Savepoint and prepared transactions

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. 3. PREPARE TRANSACTION 'uuid' 4. COMMIT PREPARED 'uuid' What if on step 2 user application issues statements with SAVEPOINTs, e.g. 2.1.