On Thu, Aug 30, 2012 at 4:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)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.
But only for 9.2, right? So people running back branches are still screwed.
The Enterprise PostgreSQL Company
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2012-08-31 03:17:55|
|Subject: Re: [HACKERS] pg_dump and thousands of schemas|
|Previous:||From: Bruce Momjian||Date: 2012-08-30 20:53:39|
|Subject: Re: pg_dump and thousands of schemas|
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2012-08-30 21:47:03|
|Subject: Re: PATCH: pgbench - aggregation of info written into log|
|Previous:||From: Robert Haas||Date: 2012-08-30 21:44:05|
|Subject: Re: PATCH: pgbench - random sampling of transaction written