Connecting to an existing transaction state.

From: Alex Gen <alexigen(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Connecting to an existing transaction state.
Date: 2008-07-28 14:37:12
Message-ID: 243951.24964.qm@web53311.mail.re2.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

I’m in the process of creating a set of scripts for testing certain locking features in an application.
What I would like to do:
1. Start a connection from machine-01 through the m01-s1.sql script.
2.While (1) is running, start another transaction on the same database from machine-02 using m02-s1.sql.

At this point in time, there are two open transactions on certain tables in the same database.

3. Using m01-s2.sql I would like to execute a certain SQL statement – BUT within the scope of the transaction begun by m01-s1.sql.
4. Current situation: Since there are several .sql scripts, each getting its own connection and executing sql stmts – they are not aware of activities of the other scripts (i.e. the open transactions).
5. What I’d like to do: After a transaction has been started from a machine, I should be able to save the transaction reference (id?) temporarily somewhere.
6. The next statement (new .sql file) that wishes to execute within the scope of the above transaction – should be able to get the transaction reference (id) and latch onto it in its current state. This way it continues to perform as part of a whole – rather than only executing the statements that it had.

Any guidance in this will help.

Cheers!
AlexiG

__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Gen 2008-07-28 14:43:24 Connecting to an existing transaction state.
Previous Message Poul Møller Hansen 2008-07-28 13:09:40 Date index not used when selecting a date range