pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jesper Pedersen <jesper.pedersen@redhat.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Jamison, Kirk <k.jamison@jp.fujitsu.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: fabriziomello@gmail.com <fabriziomello@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
Cc: Bruce Momjian <bruce@momjian.us>
Subject: Re: pg_upgrade: Pass -j down to vacuumdb
Date: Thu, 4 Apr 2019 16:20:26 +0200
Message-ID: <18557ba2-3ee7-9e17-44f2-e208d26b8640@2ndquadrant.com> (raw)
In-Reply-To: <20190403212434.GY17544@telsasoft.com>
References: <201902010958.cf2cbi3d2ule@alvherre.pgsql>
	<bef52417-2416-cb97-afce-a351601eab43@redhat.com>
	<D09B13F772D2274BB348A310EE3027C64659E9@g01jpexmbkw24>
	<CA+TgmobMGTfkMY-isz4pLw_bfywVOqTUDcW+obeAfYSeTBJM7A@mail.gmail.com>
	<03845f77-49e7-4569-7062-8ee1fb460ec2@redhat.com>
	<30470.1553551070@sss.pgh.pa.us>
	<2c054085-0b68-c049-d6d8-8b74852b4c73@2ndquadrant.com>
	<CAMkU=1zcOfThON4p00VTWEO1xdY6R8Xbh9KSt9pZkLHq0gdE=A@mail.gmail.com>
	<da27737d-9f3e-6798-c999-4adaa22c47f5@2ndquadrant.com>
	<CAMkU=1w2Yuvz+xbCU+42pT2U3GCE0xmkaSDXCgM9CR3bt=5Crw@mail.gmail.com>
	<20190403212434.GY17544@telsasoft.com>

On 2019-04-03 23:24, Justin Pryzby wrote:
> I just did a test on one of our large-but-not-huge customers.  With
> stats_target=1, analyzing a 145GB partitioned table looks like it'll take
> perhaps an hour; they have ~1TB data, so delaying services during ANALYZE would
> nullify the utility of pg_upgrade.  I can restore the essential tables from
> backup in 15-30 minutes.

I think the real fix is to have pg_upgrade copy over the statistics.
They are right there after all, just take them.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (44+ messages)  latest in thread

Message-ID: <18557ba2-3ee7-9e17-44f2-e208d26b8640@2ndquadrant.com>
Permalink:  ../18557ba2-3ee7-9e17-44f2-e208d26b8640@2ndquadrant.com/
Also on:    postgresql.org/message-id/18557ba2-3ee7-9e17-44f2-e208d26b8640@2ndquadrant.com

 · 

reply
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-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, pryzby@telsasoft.com, jeff.janes@gmail.com, tgl@sss.pgh.pa.us, jesper.pedersen@redhat.com, robertmhaas@gmail.com, k.jamison@jp.fujitsu.com, alvherre@2ndquadrant.com, michael@paquier.xyz, fabriziomello@gmail.com, pgsql-hackers@lists.postgresql.org, bruce@momjian.us
  Subject: Re: pg_upgrade: Pass -j down to vacuumdb
  In-Reply-To: <18557ba2-3ee7-9e17-44f2-e208d26b8640@2ndquadrant.com>

* 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