From: Shoaib Mir <shoaibmir@gmail.com>
To: Phillip Smith <fukawi2@iinet.net.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Backup Strategies?
Date: Tue, 6 Feb 2007 14:34:04 +0500
Message-ID: <bf54be870702060134l425e8d43m50f29e1040088f4d@mail.gmail.com> (raw)
In-Reply-To: <1170494928.9214.10.camel@phillips-desktop>
References: <1170494928.9214.10.camel@phillips-desktop>
Going with a PostgreSQL backup user (with read only permissions) seems to be
a better option for your case....
Anyone else on the list might be able to come up with much better options.
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/3/07, Phillip Smith <fukawi2@iinet.net.au> wrote:
>
> Have you looked at pg_dump and/or pg_dumpall? That would be the more
> common way of performing backups.
>
> I run 2 backup's nightly of our databases:
> 1) As part of a backup script, call pg_dumpall as the postgres *nix
> users and PG user, then pipe the output to a file on a remote server.
> 2) As a cronjob: pg_dumpall > /dev/st0
>
> Cheers,
> -p
>
>
> On Sat, 2007-02-03 at 01:51 -0500, Joshua Kramer wrote:
> > Hello All,
> >
> > What strategies are people using for automated, script-based backup of
> > databases? There are a few I can think of:
> >
> > 1. Create a "db_backup" unix user and a "db_backup" pgsql user. Grant
> > READ access to all objects on all databases for the "db_backup" pgsql
> > user. Create a .pgpass file in the home directory of the "db_backup"
> unix
> > user. Backup as needed with a script run as the "db_backup" unix user.
> >
> > 2. Create a "db_backup" unix user and repeat above, except using the
> > "postgres" db user.
> >
> > Thanks,
> > -Josh
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: Don't 'kill -9' the postmaster
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: shoaibmir@gmail.com, fukawi2@iinet.net.au
Subject: Re: Backup Strategies?
In-Reply-To: <bf54be870702060134l425e8d43m50f29e1040088f4d@mail.gmail.com>
References: <1170494928.9214.10.camel@phillips-desktop> <bf54be870702060134l425e8d43m50f29e1040088f4d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox