Re: The missing pg_get_*def functions - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: The missing pg_get_*def functions
Date
Msg-id 20130506124538.GD4361@tamriel.snowman.net
Whole thread Raw
In response to Re: The missing pg_get_*def functions  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: The missing pg_get_*def functions  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
* Dimitri Fontaine (dimitri@2ndQuadrant.fr) wrote:
> Another advantage of using more the extension infrastructure is that
> shipping bug fixes in the C or SQL parts of them would allow a hot fix
> to be shipped without restart when limited to an extension.

I'm actually not thrilled with the security update situation when it
comes to extensions.  It really is a disservice to our users to ask them
to independently manage each and every extension and upgrade each one of
them by hand.

> In-core installed-by-default extensions, anyone?

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
issues from them.  Right now we get to slide by on upgrading extensions
by not having any in-core / installed-by-default ones and punting to the
user with "well, you installed it, not us, therefore you have to manage
it by hand for eternity"; that doesn't work when we're installing it for
them and they may not even know they've got it..
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: The missing pg_get_*def functions
Next
From: Andres Freund
Date:
Subject: Re: The missing pg_get_*def functions