Re: error after dropping column - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: error after dropping column
Date
Msg-id 4B4BB2BA.1000309@postnewspapers.com.au
Whole thread Raw
In response to error after dropping column  (Filip Rembiałkowski <plk.zuber@gmail.com>)
Responses Re: error after dropping column
List pgsql-bugs
On 11/01/2010 10:27 PM, Filip Rembiałkowski wrote:
> Hi all,
>
> not sure if I should send it here; if it was reported before in
> pgsql-general. you can just ignore it :-)
>
> with postgres 8.2.4:
>
> create table test (t1 text);
> create function row2text(test) returns text as 'select $1::text'
> language sql immutable;
> create index test_row2text_idx on test( row2text(test) );
> alter table test add t2 text;
> alter table test drop t2;
> insert into test(t1) select 'foo';
>
> ERROR:  table row type and query-specified row type do not match
> DETAIL:  Physical storage mismatch on dropped attribute at ordinal
> position 2.

I'm pretty certain that's not a bug.

It's certainly a feature limitation of PostgreSQL, but it's working as
(currently) designed. You're expected to reload any functions after
dropping columns of tables.

I've seen this discusssed recently, but 8.4 still behaves the same way.

--
Craig Ringer

pgsql-bugs by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: plperl & sort
Next
From: Tom Lane
Date:
Subject: Re: error after dropping column