Re: Server Backup: pg_dump vs pg_dumpall - Mailing list pgsql-general

From Jasen Betts
Subject Re: Server Backup: pg_dump vs pg_dumpall
Date
Msg-id h49gi3$4ko$1@reversiblemaps.ath.cx
Whole thread Raw
In response to Server Backup: pg_dump vs pg_dumpall  (APseudoUtopia <apseudoutopia@gmail.com>)
List pgsql-general
On 2009-07-20, APseudoUtopia <apseudoutopia@gmail.com> wrote:
> --001636c5b16936e279046f2a9776
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
>
> Hey,
>
> I'm writing a backup script. Right now, I only have one database on my
> postgresql server. I'm deciding if I should use pg_dump or pg_dumpall when
> backing up the server. As far as I can tell, pg_dumpall cannot compress the
> dumps automatically and it only dumps data in the standard SQL text file
> format. This means that I would not be able to use pg_restore to selectively
> restore the database, correct?
>
> What is *NOT* included in a pg_dump that IS in pg_dumpall (Other than all
> the databases)? Things like user-defined functions and datatypes? Roles?
> Views?

roles mostly AIUI

> I was leaning towards pg_dumpall, but then I realized that it only dumps in
> the standard SQL text file format, and it cannot be compressed
> automatically.

you can pipe its product through your favourite stream compressor (lzma, bzip2,
gzip etc)


pgsql-general by date:

Previous
From: Jasen Betts
Date:
Subject: Re: problem with pg_restore?
Next
From: Jasen Betts
Date:
Subject: Re: table.column in query results?