Re: offset and limit in update and subselect - Mailing list pgsql-hackers

From Lincoln Yeoh
Subject Re: offset and limit in update and subselect
Date
Msg-id 3.0.5.32.20010226123939.008a0100@192.228.128.13
Whole thread Raw
In response to Re: offset and limit in update and subselect  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 11:16 PM 25-02-2001 -0500, Tom Lane wrote:
>
>Right.  Only the first row is locked, but that doesn't help any.  "order
>by random" sounds like it might be a good answer, if there aren't many
>rows that need to be sorted.

Yep. I'll just see what happens in the testing stages.

>> What would happen if I rewrite that query to:
>
>> update todo set pid = $mypid where exists ( select task id from todo where
>> pid = 0 for update limit 1);
>
>Right now you get 
>
>ERROR:  SELECT FOR UPDATE is not allowed in subselects
>
>This is something that could be fixed if FOR UPDATE were a plan node
>instead of a function done at the executor top level.

OK. Sounds like it won't be worth the trouble to do, plus deadlocks would
be real fun ;).

Cheerio,
Link.



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: pgaccess Japanese input capability patch
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] A patch for xlog.c