From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_dump and thousands of schemas
Date: Thu, 30 Aug 2012 16:53:39 -0400
Message-ID: <20120830205339.GZ8753@momjian.us> (raw)
In-Reply-To: <1086.1346359916@sss.pgh.pa.us>
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>
<20120830204433.GW8753@momjian.us>
<1086.1346359916@sss.pgh.pa.us>
On Thu, Aug 30, 2012 at 04:51:56PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Thu, May 31, 2012 at 09:20:43AM +0900, Tatsuo Ishii wrote:
> >>> 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?
>
> No, we fixed the server side instead.
Again, thanks. I knew we fixed the server, but wasn't clear that made
the client changes unnecessary, but I think I now do remember discussion
about that.
--
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, tgl@sss.pgh.pa.us, ishii@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: pg_dump and thousands of schemas
In-Reply-To: <20120830205339.GZ8753@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