From: | Jan Wieck <jan(at)wi3ck(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-24 16:05:27 |
Message-ID: | 0263bf35-05d6-02a1-519b-b7895a918314@wi3ck.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/24/21 12:04 PM, Jan Wieck wrote:
> In any case I changed the options so that they behave the same way, the
> existing -o and -O (for old/new postmaster options) work. I don't think
> it would be wise to have option forwarding work differently between
> options for postmaster and options for pg_dump/pg_restore.
Attaching the actual diff might help.
--
Jan Wieck
Principle Database Engineer
Amazon Web Services
Attachment | Content-Type | Size |
---|---|---|
pg_upgrade_improvements.v4.diff | text/x-patch | 24.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2021-03-24 16:14:21 | Re: [HACKERS] Custom compression methods |
Previous Message | Robert Haas | 2021-03-24 16:05:15 | Re: default result formats setting |