Tom Lane-2 wrote > The problem with an extension is: when we make a core change that breaks > one of these views, which we will, how can you pg_upgrade a database > with the extension installed? There's no provision for upgrading an > extension concurrently with the core upgrade. Maybe there should be, > but I'm unclear how we could make that work. > > At the same time, I'm pretty suspicious of putting stuff like this in > core, because the expectations for cross-version compatibility go up > by orders of magnitude as soon as we do that.
Why not provide a "SQL" or "Admin Scripts" directory as part of the installation that contains community "recommended" scripts for things like that? As those aren't extensions or somehow part of the data directory they don't need to be migrated and pg_upgrade does not need to take care of that. When installing a new version, the new scripts that work with the new version are installed automatically but will not overwrite the old version's scripts as the new version typically is stored in a different directory. -- View this message in context: http://postgresql.nabble.com/proposal-integration-bloat-tables-indexes-to-core-tp5907511p5908273.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
