From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER OBJECT any_name SET SCHEMA name |
Date: | 2010-10-31 16:45:53 |
Message-ID: | m2fwvme2f2.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> This reminds me of a small discussion we had some years ago when i targeted
> this for the sake of completeness of ASS (see
> <http://archives.postgresql.org/pgsql-patches/2006-06/msg00021.php>).
Discovered it, thanks for the pointer.
> I didn't follow the previous discussions about EXTENSION very closely, but
> to amend the idea made in the mentioned thread, couldn't we just invent a
> facility to move classes of objects belonging to an extension, only?
Well under the hood you still need about the same code. In the current
patch version I have, that would mean forgetting about a ~20 lines long
function and keeping the other two, 10+30 lines about.
Now if someone has a idea on how to have a single routine that knows how
to deal with any object type and change its namespace, I'm all ears, and
willing to have a try at it. Coding in C is for me a twice a year
exercise, so whatever I come up with will be... improvable, I fear.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-10-31 16:50:21 | Re: type info refactoring |
Previous Message | Tom Lane | 2010-10-31 15:44:40 | Re: why does plperl cache functions using just a bool for is_trigger |