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

help / color / mirror / Atom feed
From: Vasilis Ventirozos <v.ventirozos@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: postgresql9.4 aws - no pg_upgrade
Date: Thu, 2 Nov 2017 23:27:10 +0200
Message-ID: <F96FA87E-9234-4788-9B5D-FA3159FED7D4@gmail.com> (raw)
In-Reply-To: <CANcY5AwMvaYfwOgx=QtH-vRn=kc66W+ww7bb=uCCQGgvA0DB6w@mail.gmail.com>
References: <CANcY5AxSwhtFFfUMCKpv-6sWHzzmd4c+jYJvT=4JadHwuTLkfA@mail.gmail.com>
	<5c0dd3a9-bee1-13ce-04aa-18571b12e5c4@commandprompt.com>
	<CANcY5Ax=sd4L4d8+8KTiv3fAac3NaykMaemj7iaetiMbRtRqhg@mail.gmail.com>
	<CANcY5AxRDqUGvrgcPJnMjxxpRETrzibEyci+9o0A2t-eAhmJew@mail.gmail.com>
	<69c5d778-5d85-dc2e-c70f-5ef95b06db4f@commandprompt.com>
	<CANcY5Az=uXeXY+UAb49bGrz-cAr9g-5kE5+eq6bPUp-0f7H47g@mail.gmail.com>
	<84769c92-3364-1b03-3217-56716e3e9fff@commandprompt.com>
	<CANcY5AxTULKWfqdw=M54sHORgQMj6ZKPNdCYLwyg8+tS=xNrVg@mail.gmail.com>
	<a5deffe9-a6f5-736d-14de-044f75d94edb@commandprompt.com>
	<CANcY5Aw_T6Aqkq3Jbod=NxKGVtuawTUYGbuw9qGChzXp0QNfJg@mail.gmail.com>
	<CANcY5AyeiPnEkcC7PgoFNQMuwidrBNkNHcXVJivTKT4_Lia7hw@mail.gmail.com>
	<CANcY5AyOVvGOJX48W+s5LqkQW+knyvCafGYZXPrCeK0j-AQZFg@mail.gmail.com>
	<CANcY5AwMvaYfwOgx=QtH-vRn=kc66W+ww7bb=uCCQGgvA0DB6w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>



> On 2 Nov 2017, at 23:03, bala jayaram <balajayaram22@gmail.com> wrote:
> 
> Hi Team,
> 
> 
> We tried in production, pg_upgrade works well. But running vacuumdb , resulted in huge spike in CPU, system halted. Is there a way to fasten or parallel vacuum solution for faster recovery after pg_upgrade.
> 
> Our database size is around 500GB, contains multiple databases, huge records. What is the minimum way to do a vacuuming after pg_upgrade? This is for migration from 9.3 to 9.4.

All you need to do right after the upgrade is getting new statistics by running "analyze" or by doing something like vacuumdb -a -v -z.
That should take a while but it shouldn't "halt" anything. I believe that 9.4 doesn't have -j in vacuumdb, so you can script
something that will will get all tables, split them and run each part in X number of psqls.
When you are done with the statistics then scheduling a vacuum would be a good idea. this can be done during any convenient 
time or you can just split the work using a script.

Regards,
Vasilis Ventirozos

-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (10+ messages)  latest in thread

Message-ID: <F96FA87E-9234-4788-9B5D-FA3159FED7D4@gmail.com>
Permalink:  ../F96FA87E-9234-4788-9B5D-FA3159FED7D4@gmail.com/
Also on:    postgresql.org/message-id/F96FA87E-9234-4788-9B5D-FA3159FED7D4@gmail.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-admin@postgresql.org
  Cc: v.ventirozos@gmail.com
  Subject: Re: postgresql9.4 aws - no pg_upgrade
  In-Reply-To: <F96FA87E-9234-4788-9B5D-FA3159FED7D4@gmail.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