"Yuriy Vostrikoff" <[EMAIL PROTECTED]> writes:
> EXECUTE return wrong result after ALTER TABLE ALTER COLUMN TYPE. Is this
> expected behavior?

The prepared plan really should be invalidated by the ALTER, but we
don't currently have any infrastructure that would allow that to happen.
I think Neil Conway is looking into it for 8.2, though.

                        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

Reply via email to