| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: possibility to read dumped table's name from file |
| Date: | 2020-05-29 16:14:37 |
| Message-ID: | CAFj8pRCTBCVQhA_7SHJV9Fb4MfN=9dKkq_MhrApOdKV2=b3exg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pá 29. 5. 2020 v 18:03 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> David Fetter <david(at)fetter(dot)org> writes:
> > Would it make sense to expand this patch to handle other objects?
>
Sure. Just we should to design system (and names of options).
>
> If we're gonna do something like this, +1 for being more general.
> The fact that pg_dump only has selection switches for tables and
> schemas has always struck me as an omission.
>
a implementation is trivial, hard is good design of names for these options.
Pavel
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2020-05-29 16:38:16 | Re: pie-in-sky idea: 'sensitive' function parameters |
| Previous Message | Mark Dilger | 2020-05-29 16:13:12 | Re: speed up unicode normalization quick check |