| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] pg_dump and thousands of schemas |
| Date: | 2012-08-30 21:45:24 |
| Message-ID: | CA+TgmobHksoQmbLyAMB7D5FwqDGA8+u5rooviEuP8rg_zcMzGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-08-30 21:47:03 | Re: PATCH: pgbench - aggregation of info written into log |
| Previous Message | Robert Haas | 2012-08-30 21:44:05 | Re: PATCH: pgbench - random sampling of transaction written into log |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-08-31 03:17:55 | Re: [HACKERS] pg_dump and thousands of schemas |
| Previous Message | Bruce Momjian | 2012-08-30 20:53:39 | Re: pg_dump and thousands of schemas |