On 2013-04-30 15:57:02 +0200, Andres Freund wrote: > On 2013-04-30 05:14:15 +0100, Joel Jacobson wrote: > > On Tue, Apr 30, 2013 at 12:58 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > > Noah Misch <n...@leadboat.com> writes: > > >> Note also that minor releases can readily fix bugs in C-language > > >> functions, > > >> but we have no infrastructure to update sql-language functions after > > >> initdb. > > >> That flexibility is unfortunate to lose, particularly for something that > > >> pg_dump depends on. > > > > > > That alone would probably be sufficient reason why we would never allow > > > pg_dump to depend on any such thing (not that I see a compelling > > > argument for it to do so anyway...). > > > > It would be better to find a way to update sql-language functions in > > minor upgrades, instead of shutting that door entirely for all future > > implementation ideas involving sql-language functions in the > > pg_catalog. > > I'd be very careful with jumping on this task. I am pretty sure its a > very good way to get very, very frustrated if you don't present a widely > accepted design beforehand. Doing this correctly is *far far* from easy. > > Just a little collection of problems: > * You need to connect to all databases, not just one. There's no > infrastructure for this. > * You need to do the update *before* allowing any external > connections. Otherwise the feature won't be useful to fix actual > problems. Again, there is no infrastructure for this. > * You need to do it in a way that a) doesn't slow down normal startup b) > doesn't break if the update has only been applied to 9999 of 10000 > databases.
Another rather fundamental problem: This obviously cannot be done directly on a standby. So either we cannot rely on those updates having been performed or you need to update the standby in lockstep with the primary. Neither seems acceptable. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
