From: Bruce Momjian <bruce@momjian.us>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_dump and thousands of schemas
Date: Thu, 30 Aug 2012 16:44:33 -0400
Message-ID: <20120830204433.GW8753@momjian.us> (raw)
In-Reply-To: <20120531.092043.1953698679173443322.t-ishii@sraoss.co.jp>
References: <20120529.185149.1127748531209576379.t-ishii@sraoss.co.jp>
<12147.1338306742@sss.pgh.pa.us>
<20120530.180620.600165924826262795.t-ishii@sraoss.co.jp>
<20120531.092043.1953698679173443322.t-ishii@sraoss.co.jp>
On Thu, May 31, 2012 at 09:20:43AM +0900, Tatsuo Ishii wrote:
> >> Yeah, Jeff's experiments indicated that the remaining bottleneck is lock
> >> management in the server. What I fixed so far on the pg_dump side
> >> should be enough to let partial dumps run at reasonable speed even if
> >> the whole database contains many tables. But if psql is taking
> >> AccessShareLock on lots of tables, there's still a problem.
> >
> > Ok, I modified the part of pg_dump where tremendous number of LOCK
> > TABLE are issued. I replace them with single LOCK TABLE with multiple
> > tables. With 100k tables LOCK statements took 13 minutes in total, now
> > it only takes 3 seconds. Comments?
>
> Shall I commit to master and all supported branches?
Was this applied?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruce@momjian.us, ishii@postgresql.org, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: pg_dump and thousands of schemas
In-Reply-To: <20120830204433.GW8753@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox