On Fri, May 25, 2012 at 10:41:23AM -0400, Tom Lane wrote:
> "Hugo <Nabble>" <hugo.tech@gmail.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@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
