Stephen Frost <sfr...@snowman.net> writes: > I'm not against this idea- but we *still* need to solve the problem of > how we update the catalog during a point release and, imv anyway, we > would need to be able to upgrade any in-core installed-by-default > extensions during a point release too, to address any security or other
In case it wasn't clear, I agree with your view here and consider the capability to auto-upgrade extensions a must have. What I say is that if you ship the .so part of an extension in a live system, the next backend that starts will use that code, without a restart. That does not allow us not to provide a way to force-reload modules currently used in live backends, and we still need to be able to upgrade the system catalogs and "extension catalogs" too, either at startup in live operations. Separating away some code and SQL into in-core installed-by-default extensions means we have new problems and abilities, not that some problem are solved by themselves. 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
