Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4B1079FB460 for ; Fri, 22 Jun 2007 00:09:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 04657-01 for ; Fri, 22 Jun 2007 00:09:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id D5DCA9FB5F9 for ; Fri, 22 Jun 2007 00:09:22 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5M39KN5001156; Thu, 21 Jun 2007 20:09:23 -0700 Message-ID: <467B3DA6.4010005@commandprompt.com> Date: Thu, 21 Jun 2007 20:10:30 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Toru SHIMOGAKI CC: Tom Lane , Dan Gorman , pgsql-performance@postgresql.org Subject: Re: PITR Backups References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com> <9761.1182472005@sss.pgh.pa.us> <467B3459.9030808@oss.ntt.co.jp> In-Reply-To: <467B3459.9030808@oss.ntt.co.jp> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 21 Jun 2007 20:09:24 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/506 X-Sequence-Number: 25539 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/