From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hugo <Nabble>" <hugo(dot)tech(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pg_dump and thousands of schemas |
Date: | 2012-05-25 15:18:30 |
Message-ID: | 20120525151830.GD25444@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Fri, May 25, 2012 at 10:41:23AM -0400, Tom Lane wrote:
> "Hugo <Nabble>" <hugo(dot)tech(at)gmail(dot)com> writes:
> > If anyone has more suggestions, I would like to hear them. Thank you!
>
> Provide a test case?
>
> We recently fixed a couple of O(N^2) loops in pg_dump, but those covered
> extremely specific cases that might or might not have anything to do
> with what you're seeing. The complainant was extremely helpful about
> tracking down the problems:
> http://archives.postgresql.org/pgsql-general/2012-03/msg00957.php
> http://archives.postgresql.org/pgsql-committers/2012-03/msg00225.php
> http://archives.postgresql.org/pgsql-committers/2012-03/msg00230.php
Yes, please help us improve this! At this point pg_upgrade is limited
by the time to dump/restore the database schema, but I can't get users
to give me any way to debug the speed problems.
Someone reported pg_upgrade took 45 minutes because of pg_dumpall
--schema, which is quite long.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-25 15:19:28 | Re: pg_stat_statements temporary file |
Previous Message | Tom Lane | 2012-05-25 15:01:45 | Re: pg_stat_statements temporary file |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-05-25 15:40:04 | Re: pg_dump and thousands of schemas |
Previous Message | Craig James | 2012-05-25 15:04:18 | Re: Maximum number of sequences that can be created |