From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: Further pg_upgrade analysis for many tables |
Date: | 2012-11-12 22:17:17 |
Message-ID: | CA+U5nMLnquavqC=k1ust25O53zMo_-0BH-n1S8aOe327efDsgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12 November 2012 16:51, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Although there may be some workloads that access very large numbers of
> tables repeatedly, I bet that's not typical.
Transactions with large numbers of DDL statements are typical at
upgrade (application or database release level) and the execution time
of those is critical to availability.
I'm guessing you mean large numbers of tables and accessing each one
multiple times?
> Rather, I bet that a
> session which accesses 10,000 tables is most likely to access them
> just once each - and right now we don't handle that case very well;
> this is not the first complaint about big relcaches causing problems.
pg_restore frequently accesses tables more than once as it runs, but
not more than a dozen times each, counting all types of DDL.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-11-12 22:41:25 | Re: Further pg_upgrade analysis for many tables |
Previous Message | Andrew Dunstan | 2012-11-12 22:14:57 | vacuumlo - use a cursor |