From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Michael Monnerie <lists.michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: speedup pg_dumpall
Date: Thu, 23 Feb 2012 11:08:29 -0600
Message-ID: <4F461E2D0200002500045AC3@gw.wicourts.gov> (raw)
In-Reply-To: <2829256.7Mb1lcLYlD@saturn>
References: <2829256.7Mb1lcLYlD@saturn>
Michael Monnerie <lists.michael.monnerie@is.it-management.at> wrote:
> What can I do to improve pg_dump performance?
I can't help wondering why you're running it. For routine backups
it is generally not your best option in PostgreSQL. PITR or warm
standby are generally more useful for routine backups of any
database big enough to worry about run time.
For my purposes, pg_dump is mostly useful for dumping schema as SQL
statements or dumping data from individual tables. Prior to the
availability of pg_upgrade our main use was for upgrades from one
major release to another, but I now see it as a pretty narrow niche
utility -- at least for my shop.
-Kevin
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: Kevin.Grittner@wicourts.gov, lists.michael.monnerie@is.it-management.at
Subject: Re: speedup pg_dumpall
In-Reply-To: <4F461E2D0200002500045AC3@gw.wicourts.gov>
* 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