Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D99A12E0031 for ; Fri, 16 May 2008 12:42:09 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08501-01 for ; Fri, 16 May 2008 12:41:28 -0300 (ADT) X-Greylist: delayed 00:06:28.589027 by SQLgrey-1.7.6 Received: from mail.autorevenue.com (ip-208.178.167.106.gblx.net [208.178.167.106]) by developer.postgresql.org (Postfix) with ESMTP id 34EE42E003F for ; Fri, 16 May 2008 12:41:16 -0300 (ADT) Received: (qmail 18722 invoked from network); 16 May 2008 11:34:52 -0400 Received: from unknown (HELO dei26g028575) (msteben@10.10.1.20) by mail.autorevenue.com with SMTP; 16 May 2008 11:34:52 -0400 From: "Mark Steben" To: Subject: error message in PITR restore: Date: Fri, 16 May 2008 11:35:03 -0400 Message-ID: <006b01c8b76a$690c0170$14010a0a@dei26g028575> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C8B748.E1FF1C60" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992 Thread-Index: Aci3amjJnP28ctAHQPayaUprNxWdxw== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/145 X-Sequence-Number: 29229 This is a multi-part message in MIME format. ------=_NextPart_000_006C_01C8B748.E1FF1C60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi folks, I'm in the process of implementing PITR backups and restores and learning as I practice. I restored Using tar -xzf (backup-name) followed by restarting postgres and having the server replay the logs. I used a recovery_target_time of 1 day prior to current_date Postgres seems to come up OK but I get the following message over and over again in the serverlog: ERROR: xlog flush request F/83462374 is not satisfied --- flushed only to F/82FFF0AC CONTEXT: writing block 1242336 of relation 1663/16388/17696 The logs that came into play in the replay are (in shorthand) 80, 81, 82. The log that was copied back into xlog was 83 prior to the restore. The relation in the error message points back to a table that was indeed being updated While the backup was being done. When I attempt to do another backup I get an error that the checkpoint request failed. Is there any way replay the restore to get out of this pickle, or do I start from scratch? Fortunately this is a development server so I have the luxury of recopying production. Mark Steben Senior Database Administrator @utoRevenueT A Dominion Enterprises Company 480 Pleasant Street Suite B200 Lee, MA 01238 413-243-4800 Home Office 413-243-4809 Corporate Fax msteben @autorevenue.com Visit our new website at www.autorevenue.com IMPORTANT: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received this e-mail message in error and then delete it. Thank you. ------=_NextPart_000_006C_01C8B748.E1FF1C60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi folks,

  I’m in the process of implementing PITR backups and restores and learning as I practice. I = restored

 Using tar –xzf  (backup-name) followed by = restarting postgres and having the server replay the = logs.

  I used a recovery_target_time of 1 day prior to current_date  Postgres seems to come up OK = but

  I get the following message over and over again in the serverlog:

 

      ERROR:  xlog flush request F/83462374 is not satisfied --- flushed only to = F/82FFF0AC

     CONTEXT:  writing block 1242336 of relation 1663/16388/17696

 

  The logs that came into play in the replay are (in = shorthand)

       80, 81, 82.   The = log that was copied back into xlog was 83 prior to the = restore.

 The relation in the error message points back to a table = that was indeed being updated

 While the backup was being = done.

 

When I attempt to do another backup I get an error that the = checkpoint request failed.

 

Is there any way replay the restore to get out of this pickle, = or do I start from scratch?

 

Fortunately this is a development server so I have the luxury of recopying production.

 

 

Mark Steben

Senior Database Administrator
@utoRevenue™
A Dominion = Enterprises Company
480 = Pleasant Street
Suite = B200
Lee, MA 01238
413-243-4800 Home Office 
413-243-4809 Corporate Fax

msteben@autorevenue.com

Visit our = new website at
www.autorevenue.com

 

IMPORTANT: The information = contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is = prohibited.  If you have received this e-mail message in error, please reply to = the sender that you have received this e-mail message in error and then = delete it.  Thank you.

 

------=_NextPart_000_006C_01C8B748.E1FF1C60--