From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jerry Sievers <gsievers19@comcast.net>
Cc: Kevin Grittner <kgrittn@ymail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Dump/Reload pg_statistic to cut time from pg_upgrade?
Date: Tue, 23 Jul 2013 19:47:57 -0400
Message-ID: <20130723234757.GB31462@momjian.us> (raw)
In-Reply-To: <26325.1373474786@sss.pgh.pa.us>
References: <874nc4yi2b.fsf@comcast.net>
<1373465348.51692.YahooMailNeo@web162906.mail.bf1.yahoo.com>
<87r4f65sdm.fsf@comcast.net>
<26325.1373474786@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Wed, Jul 10, 2013 at 12:46:26PM -0400, Tom Lane wrote:
> Jerry Sievers <gsievers19@comcast.net> writes:
> > Kevin Grittner <kgrittn@ymail.com> writes:
> >> Jerry Sievers <gsievers19@comcast.net> wrote:
> >>> Planning to pg_upgrade some large (3TB) clusters using hard link
> >>> method. Run time for the upgrade itself takes around 5 minutes.
> >>> Unfortunately the post-upgrade analyze of the entire cluster is going
> >>> to take a minimum of 1.5 hours running several threads to analyze all
> >>> tables. This was measured in an R&D environment.
>
> At least for some combinations of source and destination server
> versions, it seems like it ought to be possible for pg_upgrade to just
> move the old cluster's pg_statistic tables over to the new, as though
> they were user data. pg_upgrade takes pains to preserve relation OIDs
> and attnums, so the key values should be compatible. Except in
> releases where we've added physical columns to pg_statistic or made a
> non-backward-compatible redefinition of statistics meanings, it seems
> like this should Just Work. In cases where it doesn't work, pg_dump
> and reload of that table would not work either (even without the
> anyarray problem).
Yes, we could certainly do that, but since 9.2 creates an incremental
statistics build script, I need someone to say that is too slow before I
code up something more complex.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, gsievers19@comcast.net, kgrittn@ymail.com
Subject: Re: Dump/Reload pg_statistic to cut time from pg_upgrade?
In-Reply-To: <20130723234757.GB31462@momjian.us>
References: <874nc4yi2b.fsf@comcast.net> <1373465348.51692.YahooMailNeo@web162906.mail.bf1.yahoo.com> <87r4f65sdm.fsf@comcast.net> <26325.1373474786@sss.pgh.pa.us> <20130723234757.GB31462@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