From: Khusro Jaleel <mailing-lists@kerneljack.com>
To: pgsql-admin@postgresql.org
Subject: Re: Backing up a replication set every 30 mins
Date: Wed, 15 Feb 2012 14:05:26 +0000
Message-ID: <4F3BBBA6.1040707@kerneljack.com> (raw)
In-Reply-To: <CANjgnBvJU-0C=eDkKf32YV2UrC+bVfsM8X=542T-Yn92p=vVEA@mail.gmail.com>
References: <4F3BA826.9000708@kerneljack.com>
<CANjgnBvJU-0C=eDkKf32YV2UrC+bVfsM8X=542T-Yn92p=vVEA@mail.gmail.com>
On 02/15/2012 12:58 PM, Vladimir Rusinov wrote:
>
> pg_dump won't block writes, thanks to MVCC. It may increase bloat and it
> will block DDL operations (ALTER TABLE/etc), but if your database is
> relatively small but have high load and you need frequent backups, this
> may be a way to go.
>
> --
> Vladimir Rusinov
> http://greenmice.info/
Thanks Vladimir. Would a simple script with 'pg_start_backup' and
'pg_stop_backup' and an rsync job or tar job in between would work
equally well? I thought that was the better way to do it, rather than
pg_dump?
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mailing-lists@kerneljack.com
Subject: Re: Backing up a replication set every 30 mins
In-Reply-To: <4F3BBBA6.1040707@kerneljack.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