On Sat, Dec 21, 2013 at 12:10 PM, Dimitri Fontaine <dimi...@2ndquadrant.fr> wrote: > Stephen Frost <sfr...@snowman.net> writes: >> That said, I'm starting to wonder about a few >> different options that might be handy- having the extension be dumpable >> (or maybe an option to pg_dump to dump them from the DB, or not), and >> perhaps an option to have the version # included in the dump (or an >> option to exclude it, such as when run by pg_upgrade..?). Perhaps >> similar things for pg_restore. >> >> In any case, this is certainly the way I had been hoping the discussion >> would go.. > > http://www.postgresql.org/message-id/18778.1354753...@sss.pgh.pa.us
Fortunately, nobody's proposing that exact design, and I think there are more recent emails where Tom expressed at least some support for the idea of installing an extension purely via SQL, and in fact backed the idea of being able to dump-and-restore the extension members as superior to storing blobs in the catalog. If you want to go beat your head against the wall, I don't blame you, but it's not going to help us make any progress here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
