| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | senor <frio_cervesa(at)hotmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Optimize pg_dump schema-only |
| Date: | 2019-04-29 01:19:28 |
| Message-ID: | 23800.1556500768@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
senor <frio_cervesa(at)hotmail(dot)com> writes:
> I know from a previous post to the community that pg_dump --schema-only is single threaded and the --jobs option cannot benefit pg_dump in my case (single DB, Single schema, 100000+ tables). Using pg_upgrade with the --link option is very fast except for the pg_dump portion of the upgrade which takes days.
One simple question is whether the source server is the last available
minor release (9.2.24 I believe). If not, you may be missing performance
fixes that would help. pg_dump -s on 100K tables should not take "days",
so I'm guessing you're hitting some O(N^2) behavior somewhere, and it
might be something we fixed.
Likewise make sure that pg_dump is the newest available in the destination
release series.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | senor | 2019-04-29 01:59:12 | Re: Optimize pg_dump schema-only |
| Previous Message | senor | 2019-04-28 23:54:37 | Re: Optimize pg_dump schema-only |