| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | code(at)remington(dot)io |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] pg_dumpall options proposal/patch |
| Date: | 2020-12-04 21:43:24 |
| Message-ID: | 2234516.1607118204@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
code(at)remington(dot)io writes:
> I have a relatively trivial proposal - this affects pg_dumpall exclusively. Primary use case in ability to use pg_dumpall without SUPERUSER.
> * Add --no-alter-role flag to only use CREATE ROLE syntax instead of CREATE then ALTER.
What's the point of that?
> * Likely controversial - add --merge-credentials-file which loads ROLE/PASSWORD combinations from an ini file and adds to dump output if ROLE password not present. Implemented with an external library, inih.
If it requires an external library, it's probably DOA, regardless of
whether there's a compelling use-case (which you didn't present anyway).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-12-04 21:46:34 | Re: A few new options for CHECKPOINT |
| Previous Message | Tom Lane | 2020-12-04 21:39:05 | Removal of operator_precedence_warning |