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

Re: Bug in ALTER COLUMN SET DATA TYPE ?

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Nikhil Sontakke <nikkhils(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:55:13
Message-ID: CABOikdOzm6s+wKqk_76aXGiWGRgM=4_t16=bbTWSw5JPG4jYvw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, Nov 3, 2012 at 10:21 AM, Nikhil Sontakke <nikkhils(at)gmail(dot)com> wrote:

>
>
>> 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?
>
>
Yeah, I meant  AT_PASS_OLD_CONSTR.

Thanks,
Pavan

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2012-11-03 18:45:36
Subject: gset updated patch
Previous:From: Nikhil SontakkeDate: 2012-11-03 04:51:22
Subject: Re: Bug in ALTER COLUMN SET DATA TYPE ?

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