Dimitri Fontaine <dimi...@2ndquadrant.fr> writes: > We could use get_extension_namespace() just after recoding the > dependency and error out if we don't find the arguments we gave to > recordDependencyOn() so that we're not duplicating code. That will > cover any pinned schema. I'm preparing a patch to do that.
Kids are falling asleep and the patch there: http://git.postgresql.org/gitweb?p=postgresql-extension.git;a=commitdiff;h=5d0834a8de54a52c601e4fd04aee2d19d1eef4c6 > What do we want to do with adminpack? Including its functions into > core, or have it use another schema? I don't think an extension > installing its objects into pg_catalog is that good an idea… As we're still waiting on some decision here, and some others in previous mails of this same thread, I'm waiting some more before to produce the next patch in the series. See http://archives.postgresql.org/pgsql-hackers/2011-01/msg02385.php http://archives.postgresql.org/pgsql-hackers/2011-01/msg02392.php Of course the git repository is uptodate should you want to try the newest code without waiting on me for the next patch release. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
