Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax
Date
Msg-id 10708.1369664475@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax  (Stephen Frost <sfrost@snowman.net>)
Responses Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax  (Stephen Frost <sfrost@snowman.net>)
List pgsql-bugs
Stephen Frost <sfrost@snowman.net> writes:
> * maxim.boguk@gmail.com (maxim.boguk@gmail.com) wrote:
>> It seems that documentation wrong or [ CASCADE | RESTRICT ] feature of ALTER
>> TYPE ... RENAME TO isn't implemented.

> Actually, I'm pretty sure it's implemented but the grammar for it was
> broken during refactoring to have all the ALTER .. RENAME operations go
> through the same code paths.

Are we sure the documentation's not wrong?  A quick test says this
syntax isn't accepted in *any* existing release, and I can't say I
understand what it should do anyway.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Stephen Frost
Date:
Subject: Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax
Next
From: Stephen Frost
Date:
Subject: Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax