Re: Pg_dumpall

From: <btober(at)seaworthysys(dot)com>
To: <andrewgould(at)yahoo(dot)com>
Cc: <robert(at)webtent(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pg_dumpall
Date: 2003-06-11 20:08:10
Message-ID: 64639.216.238.112.88.1055362090.squirrel@$HOSTNAME
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> I have cron execute a Python script as the database
> administrator to vacuum and backup all databases.
> Rather than dump all databases at once, however, the
> script performs a 'pgsql -l' to get a current list of
> databases. Each database is dumped and piped into
> gzip for compression into its own backup file.
>
> I should also mention that the script renames all
> previous backup files, all ending in *.gz, to
> *.gz.old; so that they survive the current pg_dump.
> Of course, you could change the script to put the date
> in the file name as to keep unlimited backup versions.

FWIW, another good way to handle the last paragraph would be to use
logrotate. It would handle renaming files as *.1, *.2,... and you could
specify the number of days you wanted it to retain and you don't have to
go in periodically and delete ancient backups so that your drive doesn't
fill up.

(US$0.02)

~Berend Tober

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Wolff III 2003-06-11 20:11:26 Re: Index not being used in MAX function (7.2.3)
Previous Message Edmund Dengler 2003-06-11 20:06:04 Re: Performance of query (fwd)