From: Joshua D. Drake <jd@commandprompt.com>
To: Toru SHIMOGAKI <shimogaki.toru@oss.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dan Gorman <dgorman@hi5.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR Backups
Date: Thu, 21 Jun 2007 20:10:30 -0700
Message-ID: <467B3DA6.4010005@commandprompt.com> (raw)
In-Reply-To: <467B3459.9030808@oss.ntt.co.jp>
References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
<9761.1182472005@sss.pgh.pa.us>
<467B3459.9030808@oss.ntt.co.jp>
Toru SHIMOGAKI wrote:
> Tom Lane wrote:
> - When we take a PITR base backup with hardware level snapshot operation
> (not filesystem level) which a lot of storage vender provide, the backup data
> can be corrupted as Dan said. During recovery we can't even read it,
> especially if meta-data was corrupted.
>
> - 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.
Joshua D. Drake
>
> So, I think users need a new feature not to write out heap pages during taking a
> backup.
>
> Any comments?
>
> Best regards,
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
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: jd@commandprompt.com, shimogaki.toru@oss.ntt.co.jp, tgl@sss.pgh.pa.us, dgorman@hi5.com
Subject: Re: PITR Backups
In-Reply-To: <467B3DA6.4010005@commandprompt.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