Re: Bug in ALTER COLUMN SET DATA TYPE ?
Nikhils <nikkhils@gmail.com>
From: Nikhil Sontakke <nikkhils@gmail.com>
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-03T04:51:22Z
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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Recast "ONLY" column CHECK constraints as NO INHERIT
- 09ff76fcdb27 9.2.0 cited
-
Adjust join_search_one_level's handling of clauseless joins.
- 1f0363001166 9.2.0 cited
-
Allow CHECK constraints to be declared ONLY
- 61d81bd28dbe 9.2.0 cited
-
Change the rules for inherited CHECK constraints to be essentially the same
- cd902b331dc4 8.4.0 cited