From: | Greg Williamson <gwilliamson39(at)yahoo(dot)com> |
---|---|
To: | APseudoUtopia <apseudoutopia(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Server Backup: pg_dump vs pg_dumpall |
Date: | 2009-07-20 22:44:04 |
Message-ID: | 318571.84487.qm@web46103.mail.sp1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi --
> 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?
The pg_dumpall gets users and groups that are not dumped in the single database versions; I used
to use pg_dump on each of several databases on a given server and then pg_dumpall with suitable
parameters to get only those bits and nothing else. User defined stuff, views etc. are all in a given
database so they will be in the pg_dump.
HTH,
Greg Williamson
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-07-20 22:45:10 | Re: Server Backup: pg_dump vs pg_dumpall |
Previous Message | David Kerr | 2009-07-20 22:44:03 | killing processes |