Skip site navigation (1) Skip section navigation (2)

Re: Bug in ALTER COLUMN SET DATA TYPE ?

From: Nikhil Sontakke <nikkhils(at)gmail(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in ALTER COLUMN SET DATA TYPE ?
Date: 2012-11-03 04:51:22
Message-ID: CANgU5Zf4ESYyC6g2BqeSpCx6q5J7-Q+t-Lc1abFcUUytEYJ-Nw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> So coming back to the issue, do you think it's a good idea to teach
> ATAddCheckConstraint() that the call is coming from a late phase of ALTER
> TABLE ?
>
> +1

You mentioned AT_PASS_OLD_INDEX in your original mail, but I guess that you
meant that we should check for  AT_PASS_OLD_CONSTR and then not raise an
error?

Regards,
Nikhils
-- 
StormDB - http://www.stormdb.com
The Database Cloud
Postgres-XC Support and Service

In response to

Responses

pgsql-hackers by date

Next:From: Pavan DeolaseeDate: 2012-11-03 04:55:13
Subject: Re: Bug in ALTER COLUMN SET DATA TYPE ?
Previous:From: Josh BerkusDate: 2012-11-03 01:44:25
Subject: Re: RFC: Timing Events

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group