Gaetano Mendola <[EMAIL PROTECTED]> writes:
> I'm playing with complex row type:
> ...
> kalman=# alter table test drop column b;
> ALTER TABLE <--- Here I think the server shall complain about
> ~ ( 7.4 doesn't complain neither )
Actually, on looking back at the code, the intention was that should
work. The DROP doesn't have to alter physical storage of the table,
so there's no need for rowtype columns in other tables to change either.
> the following select on table test1 will crash the back end
> kalman=# select * from test1;
> server closed the connection unexpectedly
Fixed --- it was just an oversight in record_out().
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
