pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jerry Sievers <gsievers19@comcast.net>
To: jmcdonagh <Joseph.E.McDonagh@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Incredibly slow restore times after 9.0>9.2 upgrade
Date: Thu, 30 Oct 2014 11:58:11 -0500
Message-ID: <86k33hwl3w.fsf@jerry.enova.com> (raw)
In-Reply-To: <1414686202058-5825052.post@n5.nabble.com>
References: <1414529739004-5824701.post@n5.nabble.com>
	<1414686202058-5825052.post@n5.nabble.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

jmcdonagh <Joseph.E.McDonagh@gmail.com> writes:

> I just had a thought- I know some of these tables are in need of a vacuuming.
> Could it be that the dump is dumping a bunch of garbage that the restore has
> to sift through on the restore? I don't know enough details to know if this
> is a dumb thought or not.

No.  However it's true that the dump will take a bit longer having to
scan a bloated table rather than a tight one.

Dump will only output the live rows.  psql or pg_restore whatever you're
using on the target side will not have to step over any junk.

HTH

>
> The restore to RDS took roughly the same amount of time. My next move is to
> try on a fast instance store, and also do a postgres 9 restore of a pure SQL
> dump, but that won't really be a great test since I use custom format. I'm
> assuming here that I can't take the custom dump from 9.2 and apply it to
> 9.0, or can I?
>
>
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/Incredibly-slow-restore-times-after-9-0-9-2-upgrade-tp582470...
> Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800


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



view thread (10+ messages)  latest in thread

Message-ID: <86k33hwl3w.fsf@jerry.enova.com>
Permalink:  ../86k33hwl3w.fsf@jerry.enova.com/
Also on:    postgresql.org/message-id/86k33hwl3w.fsf@jerry.enova.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-performance@postgresql.org
  Cc: gsievers19@comcast.net, Joseph.E.McDonagh@gmail.com
  Subject: Re: Incredibly slow restore times after 9.0>9.2 upgrade
  In-Reply-To: <86k33hwl3w.fsf@jerry.enova.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