From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com>, tony(at)exquisiteimages(dot)com |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump of database with numerous objects |
Date: | 2020-05-31 20:37:15 |
Message-ID: | 0a4039bb-bd35-d079-f124-61c4d91a81de@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/31/20 1:13 PM, Christophe Pettus wrote:
>
>
>> On May 31, 2020, at 13:10, tony(at)exquisiteimages(dot)com wrote:
>>
>> On 2020-05-31 13:08, Christophe Pettus wrote:
>>>> On May 31, 2020, at 08:05, tony(at)exquisiteimages(dot)com wrote:
>>>> My pg_class table contains 9,000,000 entries and I have 9004 schema.
>>> Which version of pg_dump are you running? Older versions (don't have
>>> the precise major version in front of me) have N^2 behavior on the
>>> number of database objects being dumped.
>>
>> I am upgrading from 9.3
>
> To which version? You might try the dump with the version of pg_dump corresponding to the PostgreSQL version you are upgrading *to* (which is recommended practice, anyway) to see if that improves matters.
Just a reminder that the OP's original issue was with using pg_upgrade.
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2020-05-31 20:38:11 | Re: pg_dump of database with numerous objects |
Previous Message | Christophe Pettus | 2020-05-31 20:13:57 | Re: pg_dump of database with numerous objects |