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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: maxim(dot)boguk(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax
Date: 2013-05-27 12:36:48
Message-ID: 20130527123648.GM8597@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Maxim,

* maxim(dot)boguk(at)gmail(dot)com (maxim(dot)boguk(at)gmail(dot)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.

> Test case:

Thanks for this. I'm working on fixing this and will also add
regression tests to, hopefully, avoid this getting broken in the future.

Thanks again,

Stephen

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-05-27 14:21:15 Re: BUG #8176: problem with the "ALTER TYPE name RENAME TO new_name [ CASCADE | RESTRICT ]" syntax
Previous Message Simon Riggs 2013-05-27 10:37:26 Re: [HACKERS] COPY .... (FORMAT binary) syntax doesn't work