2013/1/15 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> Alvaro Herrera escribió:
>> Kohei KaiGai escribió:
>>
>> > I'm probably saying same idea. It just adds invocation of external
>> > functions to check naming conflicts of functions or collation; that
>> > takes additional 4-lines for special case handling
>> > in AlterObjectNamespace_internal().
>>
>> Okay, I can agree with this implementation plan.
>
> Actually, now that I look again, this is all completely broken, because
> the "object already exists in schema foo" message is using
> getObjectDescription infrastructure, which we agree to be completely
> wrong.
>
http://www.postgresql.org/message-id/CADyhKSWVqaA6iF5wVuW5EzLaiYyCYEE2zO9guqNKy8FRdLx5Gw@mail.gmail.com

Does this patch help the trouble?
It adds ereport_on_namespace_conflict() for error message generation instead of
getObjectDescription() for ALTER RENAME primarily, but I also noticed it can be
applied on getObjectDescription() of AlterObjectNamespace_internal.

Thanks,
-- 
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>

In response to

• Re: recent ALTER whatever .. SET SCHEMA refactoring at 2013-01-15 14:21:05 from Alvaro Herrera

Responses

• Re: recent ALTER whatever .. SET SCHEMA refactoring at 2013-01-15 14:56:08 from Alvaro Herrera

pgsql-hackers by date

Next:	From: Claudio Freire	Date: 2013-01-15 14:55:31
	Subject: Re: [PATCH] COPY .. COMPRESSED
Previous:	From: Jan Wieck	Date: 2013-01-15 14:43:04
	Subject: Re: strange OOM errors with EXECUTE in PL/pgSQL