pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Léo FERLIN SUTTON <lferlin@mailjet.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Slow pg_dump affecting pg_upgrade speed
Date: Thu, 4 Jan 2018 12:53:42 -0500
Message-ID: <20180104175342.GA5478@momjian.us> (raw)
In-Reply-To: <CAOzBd94Y8-k18NNPqh8VbbG8eFSFqqC6+1jPP4bZJEWkW972bQ@mail.gmail.com>
References: <CAOzBd94Y8-k18NNPqh8VbbG8eFSFqqC6+1jPP4bZJEWkW972bQ@mail.gmail.com>

On Tue, Dec 12, 2017 at 02:24:54PM +0100, Léo FERLIN SUTTON wrote:
> We believe this is related to the size of our pg_catalog, we have
> thousands (if not hundred of thousands of views) on most of our
> databases. Here is an example on cluster A :
...
> We are completely aware that this is a *bad* idea, and our newer

I appreciate your candor.  :-)

> developments are all moving far far away for this type of schema,
> however we are currently stuck with this for at least a few more
> months if not years.
> 
> My question to this mailing list is : Are we missing something that
> could speed up the pg_dump ?

There isn't much we can do to speed it up anymore.  We optimized the
schema restore in the past, at least with the ideas we had.  A new idea
we discussed last month was to allow the schema dump/restore while the
old server is running.  You can see the discussion here:

	https://www.postgresql.org/message-id/flat/20171205140135.GA25023%40momjian.us#20171205140135.GA2502...

That is only brainstorming at this point and it is not clear we will
even implement it.

The bottom line is that pg_upgrade is much more effective on large
databases with a smaller number of database objects than the reverse.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +




view thread (2+ messages)

Message-ID: <20180104175342.GA5478@momjian.us>
Permalink:  ../20180104175342.GA5478@momjian.us/
Also on:    postgresql.org/message-id/20180104175342.GA5478@momjian.us

 · 

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: bruce@momjian.us, lferlin@mailjet.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Slow pg_dump affecting pg_upgrade speed
  In-Reply-To: <20180104175342.GA5478@momjian.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