Re: Bug in ALTER COLUMN SET DATA TYPE ? - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Bug in ALTER COLUMN SET DATA TYPE ?
Date
Msg-id CABOikdMq4RFeHXSjEdaWEWcq+tU9Lxu07QYqaQTB3R7ntvRwag@mail.gmail.com
Whole thread Raw
In response to Re: Bug in ALTER COLUMN SET DATA TYPE ?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug in ALTER COLUMN SET DATA TYPE ?  (Nikhil Sontakke <nikkhils@gmail.com>)
List pgsql-hackers



On Fri, Nov 2, 2012 at 8:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Pavan Deolasee <pavan.deolasee@gmail.com> writes:
> I noticed this behavior on master and it seems like a bug to me:

> postgres=# CREATE TABLE test (a float check (a > 10.2));
> CREATE TABLE
> postgres=# CREATE TABLE test_child() INHERITS(test);
> CREATE TABLE
> postgres=# ALTER TABLE test ALTER COLUMN a SET DATA TYPE numeric;
> ERROR:  constraint must be added to child tables too

Interestingly, this works in 8.3 and earlier ... but it fails as
described in all later versions.  So we broke it quite some time back.
It would be good to identify exactly what change broke it.


Hmm.. I haven't yet tested on other branches. But I'm surprised that you find it broken on so much old branches. "git annotate" suggests that the offending error message was added by commit 09ff76fcdb275769ac4d1a45a67416735613d04b and that commit is dated Apr 20, 2012

Thanks,
Pavan

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: unfixed bugs with extensions
Next
From: Dimitri Fontaine
Date:
Subject: Re: unfixed bugs with extensions