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

From: Dan Kortschak <dan(dot)kortschak(at)adelaide(dot)edu(dot)au>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: how to ensure a client waits for a previous transaction to finish?
Date: 2009-12-07 21:21:08
Message-ID: 1260220868.10944.11.camel@epistle
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yes, they are separate perl files (I'm thinking that perhaps this wasn't
the best way to do it now, but for the moment I'm going to have to stick
with it).

In the case of the manual testing it's jus a matter of command line
calls. The automated runs call each script as part of a PBS torque
script (essentially a sh script calls each in turn).

cheers

On Mon, 2009-12-07 at 13:16 -0800, John R Pierce wrote:
> when you say 'a series of perl scripts', do you mean separate perl
> files, each run as their own process? how are you invoking them?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dan Kortschak 2009-12-07 21:23:46 Re: how to ensure a client waits for a previous transaction to finish?
Previous Message John R Pierce 2009-12-07 21:16:05 Re: how to ensure a client waits for a previous transaction to finish?