Re: pg_upgrade failing for 200+ million Large Objects

Поиск
Список
Период
Сортировка
От Jan Wieck
Тема Re: pg_upgrade failing for 200+ million Large Objects
Дата
Msg-id 91b02dc1-f0d9-e50d-849c-18d9a66484fb@wi3ck.info
обсуждение исходный текст
Ответ на Re: pg_upgrade failing for 200+ million Large Objects  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: pg_upgrade failing for 200+ million Large Objects  (Bruce Momjian <bruce@momjian.us>)
Re: pg_upgrade failing for 200+ million Large Objects  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
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.


Regards, Jan

-- 
Jan Wieck
Principle Database Engineer
Amazon Web Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Denis Hirn
Дата:
Сообщение: Re: [PATCH] Allow multiple recursive self-references
Следующее
От: "Bossart, Nathan"
Дата:
Сообщение: Re: Change default of checkpoint_completion_target