> I have problems with moving cursors on joined tables.
Most of the more complex plan node types don't really support moving
backwards. I suppose it'd be an idea to error out rather than silently
doing the wrong thing. Fixing the code to actually do the right thing
is way down the priority list, unfortunately.
As a workaround you could modify the query to force a sort step after
the join, eg with an ORDER BY that doesn't match the join condition.
A sort node can cope with backwards scan of its output ...
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Billy O'Connor||Date: 2002-06-11 17:41:40|
|Subject: Re: Referential integrity problem postgresql 7.2 ?|
|Previous:||From: pgsql-bugs||Date: 2002-06-11 16:33:31|
|Subject: Bug #689: Bug at moving cursor on joined tables|