Re: DBI/DBD::Pg and transactions

From: "Roderick A(dot) Anderson" <raanders(at)acm(dot)org>
To:
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: DBI/DBD::Pg and transactions
Date: 2007-07-18 22:03:19
Message-ID: 469E8E27.60806@acm.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alan Hodgson wrote:
> On Wednesday 18 July 2007 14:29, "Roderick A. Anderson" <raanders(at)acm(dot)org>
> wrote:
>> In the mean time if the script gets triggered again and the first
>> instance isn't finished the second needs to not be able to select those
>> records already being handled.
>
> select for update won't do that. It will sit waiting for locks on the same
> rows the first process is handling.

Let's see how do I put it ... Da[r|m]n! But I now remember reading
something to this effect in one of my PG books or the on line docs.

Some other method is now in order.

Thanks to all for the thoughts and ideas.

I'll post my solution ... when I figure one out!

Rod
--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pat Maddox 2007-07-18 22:10:56 Re: Need help optimizing this query
Previous Message Richard Huxton 2007-07-18 22:02:51 Re: Feature request: Per database search_path