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

From APseudoUtopia
Subject Server Backup: pg_dump vs pg_dumpall
Date
Msg-id 27ade5280907201523s3a5de27ep4a74d2eb2b6c9077@mail.gmail.com
Whole thread Raw
Responses Re: Server Backup: pg_dump vs pg_dumpall
Re: Server Backup: pg_dump vs pg_dumpall
Re: Server Backup: pg_dump vs pg_dumpall
Re: Server Backup: pg_dump vs pg_dumpall
List pgsql-general
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?

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.

Thanks for any advice.

pgsql-general by date:

Previous
From: CG
Date:
Subject: Re: best practice transitioning from one datatype to another
Next
From: "Raji Sridar (raji)"
Date:
Subject: Help needed for reading postgres log : RE: Concurrency issue under very heay loads