pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua Kramer <josh@globalherald.net>
To: pgsql-admin@postgresql.org
Subject: Backup Strategies?
Date: Sat, 3 Feb 2007 01:51:56 -0500 (EST)
Message-ID: <Pine.LNX.4.64.0702030141110.1342@localhost.localdomain> (raw)


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




view thread (9+ messages)  latest in thread

Message-ID: <Pine.LNX.4.64.0702030141110.1342@localhost.localdomain>
Permalink:  ../Pine.LNX.4.64.0702030141110.1342@localhost.localdomain/
Also on:    postgresql.org/message-id/Pine.LNX.4.64.0702030141110.1342@localhost.localdomain

 · 

reply

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: josh@globalherald.net
  Subject: Re: Backup Strategies?
  In-Reply-To: <Pine.LNX.4.64.0702030141110.1342@localhost.localdomain>
  References: <Pine.LNX.4.64.0702030141110.1342@localhost.localdomain>

* 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