From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jerry Sievers <gsievers19@comcast.net>
Cc: Bruce Momjian <bruce@momjian.us>
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: Wed, 10 Jul 2013 12:46:26 -0400
Message-ID: <26325.1373474786@sss.pgh.pa.us> (raw)
In-Reply-To: <87r4f65sdm.fsf@comcast.net>
References: <874nc4yi2b.fsf@comcast.net>
<1373465348.51692.YahooMailNeo@web162906.mail.bf1.yahoo.com>
<87r4f65sdm.fsf@comcast.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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).
regards, tom lane
--
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gsievers19@comcast.net, bruce@momjian.us, kgrittn@ymail.com
Subject: Re: Dump/Reload pg_statistic to cut time from pg_upgrade?
In-Reply-To: <26325.1373474786@sss.pgh.pa.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