Re: lock table question - Mailing list pgsql-general

From Doug McNaught
Subject Re: lock table question
Date
Msg-id m3el7zl0rd.fsf@varsoon.wireboard.com
Whole thread Raw
In response to lock table question  ("Andy Kriger" <akriger@greaterthanone.com>)
Responses Re: lock table question  ("Andy Kriger" <akriger@greaterthanone.com>)
List pgsql-general
"Andy Kriger" <akriger@greaterthanone.com> writes:

> I have an inventory table. I need to be able to lock a row from being
> read/written while I: check the quantity value; modify it if necessary. From
> my experiments, it appears I can only do this with LOCK TABLE. Since this
> locks the whole table and not just the individual row, I'm guessing this
> would create quite a bottleneck if our application were larger. I'm also
> guessing that there's a better way to approach this probably common need.

Does SELECT ... FOR UPDATE not do what you want?

-Doug

pgsql-general by date:

Previous
From: "Andy Kriger"
Date:
Subject: lock table question
Next
From: Artur Rataj
Date:
Subject: Re: Boolean product of rows in multiple tables