Re: pg_dump and thousands of schemas

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: hugo(dot)tech(at)gmail(dot)com, pgsql-performance(at)postgresql(dot)org
Subject: Re: pg_dump and thousands of schemas
Date: 2012-05-26 01:18:40
Message-ID: 20120526.101840.762942175522564494.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

> "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

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-05-26 02:12:17 Re: Backends stalled in 'startup' state: index corruption
Previous Message Jeff Frost 2012-05-26 00:32:05 Re: Backends stalled in 'startup' state: index corruption

Browse pgsql-performance by date

  From Date Subject
Next Message Ivan Voras 2012-05-26 21:38:50 Seqscan slowness and stored procedures
Previous Message Ivan Voras 2012-05-25 23:56:57 Re: Parallel (concurrent) inserts?