Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 16E17D84656 for ; Fri, 8 Jun 2012 07:43:57 -0300 (ADT) Received: from nm23-vm6.bullet.mail.sg3.yahoo.com ([106.10.151.69]) by magus.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1ScwfZ-0000EF-OJ for pgsql-admin@postgresql.org; Fri, 08 Jun 2012 10:43:56 +0000 Received: from [106.10.166.121] by nm23.bullet.mail.sg3.yahoo.com with NNFMP; 08 Jun 2012 10:43:36 -0000 Received: from [106.10.150.29] by tm10.bullet.mail.sg3.yahoo.com with NNFMP; 08 Jun 2012 10:43:36 -0000 Received: from [127.0.0.1] by omp1030.mail.sg3.yahoo.com with NNFMP; 08 Jun 2012 10:43:36 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 330630.63667.bm@omp1030.mail.sg3.yahoo.com Received: (qmail 5951 invoked by uid 60001); 8 Jun 2012 10:43:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.cn; s=s1024; t=1339152214; bh=0ea0+UwQ4w2dW5aigQB90EbnrLGho4UcPkRV1z1F+FI=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=MyNH4g9kKsJmnC/npJA05MlvAd8bng9zdG7igw/OpPyGe9iXqOHYniy++BQHenGn7XFG4a12sqeRIKvwKIy/yVy8hZaey82cq2E7kTyRcfSB9dXStkwJEc7MxWEw2H5lzvt7/0kfenWJiXwaWWhjlhNtL5Y6CkSZBWQBoVt9MSA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=aFMqaf6T226QLGIxky/1Mu7YrhS74Vd/fUnRJSfuaWG5fgPLkOqSHK/McZGmmUKxPO8Z2NIIkvyHp8B85v1sgJoo/9lr1eILBMa6van9f4TQQQ+P3mLb8kN8xiCyVPp+bXPh/5cGYBLxuAtZX4nvinYXP5+L156jNWWltyZPlrA=; X-YMail-OSG: MBaOawsVM1lLlLI4Li0b7Y98aRWLGSonN_CfHjE2EkHN9gM PORfGgp78HxE.Wj80QKGRvqb1G9UrPjqhVAPUm9jUYqThX3zhZZ9FTLhsEO. X5ZYpqV2hHEeA1WeY7DgsTiyCGn4LnuHjReNgan46RIVIKXTMxK2_ZVBTuKa z85rxssMdY1GMfqDkt95wXv.olbgfKM06AuGc0RO1jxhO7_xcpMt4ivP.W72 A82b2pBTRCNWuRVRWKnh7t5L49nL54vBhQos9r60.iu2OUB0ph65vDt8zwrP 83MD6uqQJmPHjzJOcMSTajIfI7d6m59sJ1izaP5IM4V6i_mwSfLYve71aFr0 .zOf0NmGtOiNojsJBRzflpVr.a.qwNY3rQ625_zDNxU8jWlNGUcHpi8WKAyy l0QzFL8Epk7RLBin4n4Jza.oyX59xJR.4 Received: from [218.241.169.34] by web15601.mail.cnb.yahoo.com via HTTP; Fri, 08 Jun 2012 18:43:34 CST X-Mailer: YahooMailClassic/15.0.6 YahooMailWebService/0.8.118.349524 Message-ID: <1339152214.5566.YahooMailClassic@web15601.mail.cnb.yahoo.com> Date: Fri, 8 Jun 2012 18:43:34 +0800 (CST) From: sgm Subject: Question about PITR backup To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="940083559-295342153-1339152214=:5566" X-Pg-Spam-Score: 1.0 (+) X-Archive-Number: 201206/36 X-Sequence-Number: 39627 --940083559-295342153-1339152214=:5566 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Dear admin, I have a question about PITR backup in a single server, the method is make = a base backup, and backup the WAL archive log(eg, every day at 11:30 pm). B= ut if the OS' harddisk is broken(eg,14:00 pm),the system can't start, we ha= ve to recover the database on a another server using the base backup and th= e WAL backup,so in this case suppose that we only can restore the database = to yesterday's 11:30 pm state, am I right?=A0 How can we recover the database to 14:00 pm? We are missing the newest pg_x= log. I want to backup the pg_xlog folder every minute by crontab but my concern = is that the data inconsistent, because the lastest log in pg_xlog is being = updated all the time, am I right? =A0 Any suggestions? Very appreciated your answer. Thanks, Song=A0 --940083559-295342153-1339152214=:5566 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Dear admin,

I have a quest= ion about PITR backup in a single server, the method is make a base backup,= and backup the WAL archive log(eg, every day at 11:30 pm). But if the OS' = harddisk is broken(eg,14:00 pm),the system can't start, we have to recover = the database on a another server using the base backup and the WAL backup,s= o in this case suppose that we only can restore the database to yesterday's= 11:30 pm state, am I right? 

How can we reco= ver the database to 14:00 pm? We are missing the newest pg_xlog.
=
I want to backup the pg_xlog folder every minute by crontab = but my concern is that the data inconsistent, because the lastest log in pg= _xlog is being updated all the time, am I right?   Any suggestions?

Very appreciated your answer.

Thanks,

Song&nbs= p;
--940083559-295342153-1339152214=:5566--