Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 48833B53E85 for ; Fri, 25 May 2012 11:41:37 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SXvhw-0002v0-Gq for pgsql-performance@postgresql.org; Fri, 25 May 2012 14:41:36 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q4PEfNhD020888; Fri, 25 May 2012 10:41:23 -0400 (EDT) To: "Hugo " cc: pgsql-performance@postgresql.org Subject: Re: pg_dump and thousands of schemas In-reply-to: <1337921645663-5709975.post@n5.nabble.com> References: <1337843209018-5709766.post@n5.nabble.com> <20120525035455.GC25444@momjian.us> <1337921645663-5709975.post@n5.nabble.com> Comments: In-reply-to "Hugo " message dated "Thu, 24 May 2012 21:54:05 -0700" Date: Fri, 25 May 2012 10:41:23 -0400 Message-ID: <20887.1337956883@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201205/139 X-Sequence-Number: 46963 "Hugo " 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 regards, tom lane