From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | APseudoUtopia <apseudoutopia(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Server Backup: pg_dump vs pg_dumpall |
Date: | 2009-07-20 22:45:10 |
Message-ID: | dcc563d10907201545i394ebf48vd3f112ff28460b81@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jul 20, 2009 at 4:23 PM, APseudoUtopia<apseudoutopia(at)gmail(dot)com> wrote:
> 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.
I use pg_dump on databases and pg_dumpall --globals to get the user
accounts and such.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-07-20 22:48:17 | Re: killing processes |
Previous Message | Greg Williamson | 2009-07-20 22:44:04 | Re: Server Backup: pg_dump vs pg_dumpall |