Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> Please find attached v12 of the patch, which implements that idea.

And v13 now. v12 was intended to see what you think about the new
pg_execute_from_file placeholder API and replace_text usage, v13 fixes
the pg_dump support by adding dependencies.

Also, I've been changing the \dx output to show the schema where an
extension's objects are living rather than the custom_variable_classes
that most users won't care about, I think.

Then, I think the ALTER EXTENSION foo SET SCHEMA name still has a use
case, so I've prepared a simple patch to show the API usage before we
get to refactor it all following Tom's asking. So there's a initial
patch to see that in action. I had to rework AlterFunctionNamespace()
API so that I can call it from elsewhere in the backend where I have
Oids, so here's an updated set_schema.4.patch. We will have to extend
the APIs for relations and types the same way, but it's already possible
to test the patch with some extensions this way.

Producing those patches (the alter_extension patch is an incremental
patch that sits atop both the extension and the set_schema one) is made
easy enough with git, I'm impressed by this tool.

  http://git.postgresql.org/gitweb?p=postgresql-extension.git;a=summary

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

In response to

• Re: ALTER OBJECT any_name SET SCHEMA name at 2010-11-02 13:03:44 from Dimitri Fontaine

Responses

• Re: ALTER OBJECT any_name SET SCHEMA name at 2010-11-03 21:18:32 from Alvaro Herrera

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2010-11-03 16:28:42
	Subject: Re: why does plperl cache functions using just a bool for is_trigger
Previous:	From: Tom Lane	Date: 2010-11-03 14:42:12
	Subject: Re: improved parallel make support