> "Hugo <Nabble>" <hugo.tech@xxxxxxxxx> 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 I'm wondering if these fixes (or today's commit) include the case for a database has ~100 thounsands of tables, indexes. One of my customers has had troubles with pg_dump for the database, it takes over 10 hours. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
