Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 92740A5CB39 for ; Wed, 15 Feb 2012 10:05:41 -0400 (AST) Received: from kerneljack.com ([89.16.173.229]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RxfUJ-0005yo-3D for pgsql-admin@postgresql.org; Wed, 15 Feb 2012 14:05:40 +0000 Received: from [217.33.138.50] (helo=telnic-19.telnic.local) by kerneljack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1RxfU4-0006tv-K0 for pgsql-admin@postgresql.org; Wed, 15 Feb 2012 14:05:24 +0000 Message-ID: <4F3BBBA6.1040707@kerneljack.com> Date: Wed, 15 Feb 2012 14:05:26 +0000 From: Khusro Jaleel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120131 Thunderbird/10.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Backing up a replication set every 30 mins References: <4F3BA826.9000708@kerneljack.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201202/63 X-Sequence-Number: 39123 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?