Re: Upgrading cluster with thousands of DBs

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alejandro Martínez <zen(at)itram(dot)es>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Upgrading cluster with thousands of DBs
Date: 2014-01-22 02:05:39
Message-ID: 20140122020539.GB5322@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Jan 14, 2014 at 11:45:33AM +0100, Alejandro Martínez wrote:
> Hi list,
>
> We're working on upgrading from 9.1 to 9.3 some of our database
> clusters, while seeking to minimize (write) downtime by making the
> upgrades as fast as possible.
>
> However, our clusters have the particularity that they get to host
> many different *databases*, as in, ~2000 databases per cluster. Most
> of those databases are small (only a table and PostGIS functions), so
> it's more a problem of the number of DBs than the space they use. The
> total size of the cluster is around 60gb.
>
> I first started using pg_upgrade but, even when enabling
> parallelization and hardlinks, as most of the steps (preliminary
> check?) don't seem to be parallelized, the upgrade takes ~5 hours as
> it goes database-per-database serially on most steps.

That is surprising. I know I see parallel hard link creation and
parallel database dump in my testing of 9.3 pg_upgrade.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2014-01-24 15:03:01 Easy way to know the original table row/column given a pg_toast.pg_toast_XXXX chunk_id ?
Previous Message sparikh 2014-01-21 17:45:11 Re: pg_ctl promote