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: pgsql-general(at)postgresql(dot)org
Subject: Re: how to ensure a client waits for a previous transaction to finish?
Date: 2009-12-09 03:13:24
Message-ID: 1260328404.22256.26.camel@zoidberg.mbs.adelaide.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I've spoken to people on the torque user mailing list and tried merlin's
suggestion below (which looked like it should work - but unfortunately
did not prevent the problem).

>From working through things with the torque list, it seems to be the
case that postgresql is behaving differently because it is not attached
to a terminal (this has caused problems for others on that list with
sqlite and mysql).

Can anyone confirm/refute this? And if it is the case, is there
something that I can do about it?

thanks again.
Dan

On Mon, 2009-12-07 at 18:33 -0500, Merlin Moncure wrote:
> If it turns out you need to have a lock with a 'longer than
> transaction' duration, maybe advisory locks are a good fit.
>
> merlin
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-12-09 03:53:41 Re: Installing PL/pgSQL by default
Previous Message Tom Lane 2009-12-09 03:04:54 Re: regexp_matches() quantified-capturing-parentheses oddity