pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Speeding up pg_dump
Date: Tue, 14 Dec 2004 23:11:27 +0000
Message-ID: <1103065887.4037.3762.camel@localhost.localdomain> (raw)
In-Reply-To: <1103045806.25186.153.camel@home>
References: <1103045806.25186.153.camel@home>

On Tue, 2004-12-14 at 17:36, Rod Taylor wrote:
> Are there any tricks to speeding up pg_dump aside from doing them from a
> replicated machine?
> 
> I'm using -Fc with no compression.

Run a separate pg_dump for larger tables and run them concurrently so
you use more cpu and disk resources.

The lower compression levels are fast and nearly as good (in my testing)
as full compression. Using compression tends to use up the CPU that
would otherwise be wasted since the pg_dump is disk intensive, and then
saves further I/O by reducing the output file size.

-- 
Best Regards, Simon Riggs




view thread (2+ messages)

Message-ID: <1103065887.4037.3762.camel@localhost.localdomain>
Permalink:  ../1103065887.4037.3762.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1103065887.4037.3762.camel@localhost.localdomain

 · 

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: simon@2ndquadrant.com, pg@rbt.ca
  Subject: Re: Speeding up pg_dump
  In-Reply-To: <1103065887.4037.3762.camel@localhost.localdomain>

* 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