Re: speedup pg_dumpall - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: speedup pg_dumpall
Date
Msg-id 4F461E2D0200002500045AC3@gw.wicourts.gov
Whole thread Raw
In response to speedup pg_dumpall  (Michael Monnerie <lists.michael.monnerie@is.it-management.at>)
Responses Re: speedup pg_dumpall  (Michael Monnerie <lists.michael.monnerie@is.it-management.at>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Brian Fehrle
Date:
Subject: Re: WAL files containing old and unmodified data?
Next
From: "Fred Parkinson"
Date:
Subject: Can't query the sequence table of a serial primary key.