Re: SQL objects UNITs - Mailing list pgsql-hackers

From Robert Haas
Subject Re: SQL objects UNITs
Date
Msg-id CA+Tgmoa1bQkVXEq57TtRLww7LRQ2c5MvqyJP1+FLxx3q6AnhcA@mail.gmail.com
Whole thread Raw
In response to Re: SQL objects UNITs  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: SQL objects UNITs
List pgsql-hackers
On Sat, Dec 21, 2013 at 12:10 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Stephen Frost <sfrost@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.1354753982@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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WITHIN GROUP patch
Next
From: Tom Lane
Date:
Subject: Re: SQL objects UNITs