| From: | APseudoUtopia <apseudoutopia(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Server Backup: pg_dump vs pg_dumpall |
| Date: | 2009-07-20 22:23:23 |
| Message-ID: | 27ade5280907201523s3a5de27ep4a74d2eb2b6c9077@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raji Sridar (raji) | 2009-07-20 22:33:04 | Help needed for reading postgres log : RE: Concurrency issue under very heay loads |
| Previous Message | Bruce Momjian | 2009-07-20 22:06:57 | Re: [GENERAL] large object does not exist after pg_migrator |