Search Postgresql Archives

how to ensure a client waits for a previous transaction to finish?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, this is a bit of a noob question.

I am using PGSql to perform some large analyses, with the clients being
a sequentially run set of perl scripts (one to set up and populate
tables and then down stream scripts to query the database for the
results).

During manual testing everything works, but automating it results in the
query scripts starting before the population transactions having
completed, so they give erroneous result.

How can I ensure the query scripts wait until the population transaction
processes have finished? I've looked at 'SET TRANSACTION ISOLATION LEVEL
SERIALIZABLE' (to us in the query scripts I thought), but I'm not sure
that is what I want.

Can any one suggest where I should be looking, or if SET TRANSACTION is
the right way to go?

thanks


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux