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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: maxim(dot)boguk(at)gmail(dot)com, 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 14:25:09
Message-ID: 20130527142509.GU8597@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> 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.

Was just composing an email to that effect, actually. I agree that it's
a documentation issue. Of course, that makes it easier to fix. :)

Thanks,

Stephen

In response to

Browse pgsql-bugs by date

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