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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-hackers by date

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