| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Lætitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, Ryan Lambert <ryan(at)rustprooflabs(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, ahsan hadi <ahsan(dot)hadi(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Date: | 2022-03-25 21:09:33 |
| Message-ID: | E0BBFD75-0337-4077-AC06-F77CDD2CD58F@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Mar 2022, at 01:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| 0001-First-WIP-stab-at-exclude-extension-for-pg_dump.patch | application/octet-stream | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2022-03-25 21:18:29 | Re: SQL/JSON: JSON_TABLE |
| Previous Message | David G. Johnston | 2022-03-25 21:02:02 | Re: Document atthasmissing default optimization avoids verification table scan |