Re: recent ALTER whatever .. SET SCHEMA refactoring - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: recent ALTER whatever .. SET SCHEMA refactoring
Date
Msg-id 20130115142105.GC4146@alvh.no-ip.org
Whole thread Raw
In response to Re: recent ALTER whatever .. SET SCHEMA refactoring  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: recent ALTER whatever .. SET SCHEMA refactoring
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Teaching pg_receivexlog to follow timeline switches
Next
From: Peter Eisentraut
Date:
Subject: Re: system administration functions with hardcoded superuser checks