| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Laetitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Vik Fearing <vik(at)postgresfriends(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Date: | 2022-03-25 17:56:42 |
| Message-ID: | 3386445.1648231002@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> I don't find the --objectype-only option to be desirable. psql
> --tables-only --functions-only just seems odd, no longer are they "only".
> I would go with --function-all (and maybe --function-system and
> --function-user) if going down this path but the wildcard feature can
> handle this just fine and we want that feature anyway.
Agreed. "--function=*" is more general than "--function-only",
and shorter too, so what's not to like?
> Except succinctly
> omitting system objects which should get its own general option.
pg_dump never dumps system objects, so I don't see a need for
a switch to tell it not to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-03-25 18:29:08 | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Previous Message | Robert Haas | 2022-03-25 17:52:11 | Re: pgsql: Add 'basebackup_to_shell' contrib module. |