Re: pg_dump new feature: exporting functions only. Bad or good idea ? - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Date
Msg-id E0BBFD75-0337-4077-AC06-F77CDD2CD58F@yesql.se
Whole thread Raw
In response to Re: pg_dump new feature: exporting functions only. Bad or good idea ?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump new feature: exporting functions only. Bad or good idea ?  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> On 25 Mar 2022, at 01:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> The extension object type does not seem to have gotten the
>> --exclude-extension capability that it would need to conform to the general
>> design exemplified by --table and hopefully extended out to the routine
>> object types.
>
> We're not going to instantly build out every feature that would be
> suggested by a roadmap.

Agreed.  In this case it seems that adding --exclude-extension would make sense
to keep conistency.  I took a quick stab at doing so with the attached while
we're here.

--
Daniel Gustafsson        https://vmware.com/


Attachment

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Document atthasmissing default optimization avoids verification table scan
Next
From: Zhihong Yu
Date:
Subject: Re: SQL/JSON: JSON_TABLE