Re: BUG #14470: Dropping a column produces "table row type and query-specified row type do not match" error

joan(at)sanchezsabe(dot)com writes:
> At this point, if we drop one column (not used at all by the previous
> function)...
> ALTER TABLE users
> DROP COLUMN column_that_we_will_drop ;
> ... this makes the next statement to generate an error
> SELECT * FROM fun('a(at)b(dot)com');
> ERROR: table row type and query-specified row type do not match
> SQL state: 42804
> Detail: Query provides a value for a dropped column at ordinal position 3.
> Context: SQL function "fun" statement 1
> SELECT * FROM fun('a(at)b(dot)com');

I can't reproduce this in HEAD or 9.6 branch tip. I believe it was
already fixed by this patch, which went in a bit after 9.6.1:

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=f4d865f22

But thanks for the report!

regards, tom lane