Re: UPDATE/DELETE XXX WHERE CURRENT OF cursor_name - Mailing list pgsql-hackers

From Tom Lane
Subject Re: UPDATE/DELETE XXX WHERE CURRENT OF cursor_name
Date
Msg-id 11321.1153756300@sss.pgh.pa.us
Whole thread Raw
In response to Re: UPDATE/DELETE XXX WHERE CURRENT OF cursor_name  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: UPDATE/DELETE XXX WHERE CURRENT OF cursor_name  ("Florian G. Pflug" <fgp@phlo.org>)
List pgsql-hackers
"Florian G. Pflug" <fgp@phlo.org> writes:
> How could there be a concurrent update of the _same_ row, when
> I do "select * from bar *for update*".

AFAICT the spec doesn't require one to have written FOR UPDATE
in order to use WHERE CURRENT OF.  (In effect, they expect FOR UPDATE
to be the default, which is certainly not a change we're going to
want to make to DECLARE CURSOR.)  If we did make that restriction
then we could probably skip the EvalPlanQual mess.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UPDATE/DELETE XXX WHERE CURRENT OF cursor_name
Next
From: Tom Lane
Date:
Subject: Re: Better name/syntax for "online" index creation