From: Michael Monnerie <lists.michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Subject: Re: speedup pg_dumpall
Date: Wed, 07 Mar 2012 17:52 +0100
Message-ID: <2933170.uCZf1iJOXt@saturn> (raw)
In-Reply-To: <4F461E2D0200002500045AC3@gw.wicourts.gov>
References: <2829256.7Mb1lcLYlD@saturn>
<4F461E2D0200002500045AC3@gw.wicourts.gov>
Am Donnerstag, 23. Februar 2012, 11:08:29 schrieb Kevin Grittner:
> > 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.
We're a hoster, so usually each database belongs to a different
customer. Each customer can have a "get a dump of our database daily"
dump. Also, restoring a single db is simpler when you got a dump of it.
> 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.
Agreed, for a classical db server this could be better. We need the
per-db dumps, so pg_dump performance tuning would be nice. It's quite
slow currently. Someone got hints what to do against that?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
Attachments:
signature.asc (application/pgp-signature, 197B) download
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: lists.michael.monnerie@is.it-management.at, Kevin.Grittner@wicourts.gov
Subject: Re: speedup pg_dumpall
In-Reply-To: <2933170.uCZf1iJOXt@saturn>
* 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