| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jan Wieck <jan(at)wi3ck(dot)info> |
| Cc: | Zhihong Yu <zyu(at)yugabyte(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Robins Tharakan <tharakan(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade failing for 200+ million Large Objects |
| Date: | 2021-03-23 18:25:01 |
| Message-ID: | 20210323182501.GH579@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 23, 2021 at 02:23:03PM -0400, Jan Wieck wrote:
> On 3/23/21 2:06 PM, Bruce Momjian wrote:
> > We have the postmaster which can pass arbitrary arguments to postgres
> > processes using -o.
>
> Right, and -o is already taken in pg_upgrade for sending options to the old
> postmaster.
>
> What we are looking for are options for sending options to pg_dump and
> pg_restore, which are not postmasters or children of postmaster, but rather
> clients. There is no option to send options to clients of postmasters.
>
> So the question remains, how do we name this?
>
> --pg-dump-options "<string>"
> --pg-restore-options "<string>"
>
> where "<string>" could be something like "--whatever[=NUM] [...]" would be
> something unambiguous.
Sure. I don't think the letter you use is a problem.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-03-23 18:28:50 | Re: WIP: BRIN multi-range indexes |
| Previous Message | Bossart, Nathan | 2021-03-23 18:24:07 | Re: Change default of checkpoint_completion_target |