pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Toru SHIMOGAKI <shimogaki.toru@oss.ntt.co.jp>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dan Gorman <dgorman@hi5.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR Backups
Date: Fri, 22 Jun 2007 16:41:24 +0900
Message-ID: <467B7D24.3040802@oss.ntt.co.jp> (raw)
In-Reply-To: <467B3DA6.4010005@commandprompt.com>
References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
	<9761.1182472005@sss.pgh.pa.us>
	<467B3459.9030808@oss.ntt.co.jp>
	<467B3DA6.4010005@commandprompt.com>


Joshua D. Drake wrote:

>> - If we don't use hardware level snapshot operation, it takes long time to take
>>   a large backup data, and a lot of full-page-written WAL files are made.
> 
> Does it? I have done it with fairly large databases without issue.

You mean hardware snapshot? I know taking a backup using rsync(or tar, cp?) as a
n online backup method is not so a big problem as documented. But it just take a
long time if we handle a terabyte database. We have to VACUUM and other batch
processes  to the large database as well, so we don't want to take a long time
to take a backup...

Regards,

-- 
Toru SHIMOGAKI<shimogaki.toru@oss.ntt.co.jp>
NTT Open Source Software Center




view thread (38+ messages)  latest in thread

Message-ID: <467B7D24.3040802@oss.ntt.co.jp>
Permalink:  ../467B7D24.3040802@oss.ntt.co.jp/
Also on:    postgresql.org/message-id/467B7D24.3040802@oss.ntt.co.jp

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: shimogaki.toru@oss.ntt.co.jp, jd@commandprompt.com, tgl@sss.pgh.pa.us, dgorman@hi5.com
  Subject: Re: PITR Backups
  In-Reply-To: <467B7D24.3040802@oss.ntt.co.jp>

* 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