Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
Date: 2011-11-18 00:13:50
Message-ID: 14492.1321575230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Nov 17, 2011 at 5:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I still think it's reasonable to remove the extra downcasing step,
>> but we'll have to document it as a change.

> So, should we add a note to all the LANGUAGE command pages in the
> manual? Or just include this in the release notes?

Release note seems sufficient. I looked at the text in CREATE FUNCTION
and it doesn't seem to need changing.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-11-18 01:59:58 Re: RangeVarGetRelid()
Previous Message Royce Ausburn 2011-11-18 00:05:46 Re: [PATCH] Unremovable tuple monitoring