"Sergey Manakov" <vial...@gmail.com> writes: > alter table biz_uks > drop column remark > ;
> create or replace function set__biz_uks() > returns setof biz_uks > security definer volatile language plpgsql as $$ > declare > res biz_uks; > begin > return query > select res.*; > end; > $$ ; Yeah, plpgsql has never been tremendously good with rowtypes containing dropped columns. There is a fix in CVS HEAD that deals with this case http://archives.postgresql.org/pgsql-committers/2009-08/msg00068.php but it was deemed too invasive to risk back-patching. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
