pg_upgrade on high number tables database issues

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: pg_upgrade on high number tables database issues
Date: 2014-03-10 13:58:22
Message-ID: CAFj8pRAv_hr5BoPjogg_dD=D_iHjK3KJCA4DgMh+uZnVzBzn7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

I had to migrate our databases from 9.1 to 9.2. We have high number of
databases per cluster (more than 1000) and high number of tables (indexes)
per database (sometimes more than 10K, exceptionally more than 100K).

I seen two problems:

a) too long files pg_upgrade_dump_db.sql, pg_upgrade_dump_all.sql in
postgres HOME directory. Is not possible to change a directory for these
files.

b) very slow first stage of upgrade - schema export is very slow without
high IO or CPU utilization.

Regards

Pavel

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-03-10 14:26:23 Re: on_exit_reset fails to clear DSM-related exit actions
Previous Message Michael Paquier 2014-03-10 12:47:27 Re: Standby node using replication slot not visible in pg_stat_replication while catching up