Thomas Jacob <jacob(at)internet24(dot)de> writes:
> I've run into some weirdness in PSQL 8.3.8 (Ubuntu 8.04 LTS x86_64
> package). When I update a row while using a function result
> that updates that very same row in the "WHERE" part of the update,
> the main update no longer takes place, even though the "WHERE"
> conditions should match. But if I execute
> the function before the update, and then do the update
> based on the same logic, I see both changes.
This is expected; it's worked like that since Berkeley days.
An UPDATE will not touch a row that's already been updated
within your own transaction since the UPDATE started. This
is mainly to avoid sorceror's-apprentice syndrome with repeatedly
updating the same row.
In general, having side-effects in a function invoked in WHERE
is a dangerous and unwise practice anyhow, IMNSHO. You have
very little control over when or even whether the side effects
In the particular case at hand, you might want to think about
using SELECT FOR UPDATE locking instead of rolling your own.
SELECT * FROM tab WHERE id = x FOR UPDATE;
... do some work using retrieved values ...
UPDATE tab SET ... WHERE id = x;
has simple and reliable behavior.
regards, tom lane
In response to
pgsql-general by date
|Next:||From: John R Pierce||Date: 2009-09-30 14:43:16|
|Subject: Re: ms-sql -> pg 8.x|
|Previous:||From: Tom Lane||Date: 2009-09-30 13:55:55|
|Subject: Re: Where can I get the number of plans that considered by Planner? |