Re: pg_upgrade failing for 200+ million Large Objects - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade failing for 200+ million Large Objects
Date
Msg-id 20210323182501.GH579@momjian.us
Whole thread Raw
In response to Re: pg_upgrade failing for 200+ million Large Objects  (Jan Wieck <jan@wi3ck.info>)
List 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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.




pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: Change default of checkpoint_completion_target
Next
From: Alvaro Herrera
Date:
Subject: Re: WIP: BRIN multi-range indexes