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.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

• Re: recent ALTER whatever .. SET SCHEMA refactoring at 2013-01-14 22:27:53 from Alvaro Herrera

Responses

• Re: recent ALTER whatever .. SET SCHEMA refactoring at 2013-01-15 14:48:47 from Kohei KaiGai

pgsql-hackers by date

Next:	From: Peter Eisentraut	Date: 2013-01-15 14:25:40
	Subject: Re: system administration functions with hardcoded superuser checks
Previous:	From: Heikki Linnakangas	Date: 2013-01-15 14:05:57
	Subject: Teaching pg_receivexlog to follow timeline switches