Re: Optimize pg_dump schema-only

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Optimize pg_dump schema-only
Date: 2019-04-28 21:54:19
Message-ID: 6788.1556488459@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> On 4/28/19 3:21 PM, senor wrote:
>> I see only one CPU of 32 doing anything and it's often at 100%. Disk IO
>> is minimal. Memory use varies but always plenty to spare.

> "pg_dump --schema-only" is single-threaded.

Yup. But ...

pg_upgrade does have a --jobs option, since 9.5 or so. What it does
is to run the dump and restore tasks for different databases of the
cluster in parallel. So it won't help much if you've just got one
DB with a lotta objects, but I thought it was worth mentioning.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message senor 2019-04-28 23:54:37 Re: Optimize pg_dump schema-only
Previous Message Ron 2019-04-28 21:08:41 Re: Optimize pg_dump schema-only