Re: error after dropping column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: error after dropping column
Date: 2010-01-12 00:12:45
Message-ID: 21828.1263255165@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> On 11/01/2010 10:27 PM, Filip Rembiakowski wrote:
>> 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.

No, it is a bug, or at least an overlooked case. There might be some
variants of this that aren't readily fixable, but that one is/was:
http://archives.postgresql.org/pgsql-committers/2010-01/msg00168.php

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-01-12 02:31:57 Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
Previous Message Craig Ringer 2010-01-11 23:22:34 Re: error after dropping column