Vlad <marchenko@xxxxxxxxx> writes:
> yes, we actually use table alias as a workaround, I thought that it's
> actually looks like error in postgresql parser (or deeper) that needs
> to be reported.
No, it's supposed to be that way: FOR UPDATE items are table aliases.
Perhaps this isn't adequately documented...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
