From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Server Backup: pg_dump vs pg_dumpall |
Date: | 2009-07-23 11:12:03 |
Message-ID: | h49gi3$4ko$1@reversiblemaps.ath.cx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2009-07-20, APseudoUtopia <apseudoutopia(at)gmail(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2009-07-23 11:28:56 | Re: table.column in query results? |
Previous Message | Jasen Betts | 2009-07-23 10:47:40 | Re: problem with pg_restore? |