Re: Recreating archive_status - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Recreating archive_status
Date
Msg-id 200803180237.m2I2bIq23600@momjian.us
Whole thread Raw
In response to Recreating archive_status  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Added to TODO:
       o Recreate pg_xlog/archive_status/ if it doesn't exist after         restoring from a PITR backup
         http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php


---------------------------------------------------------------------------

Simon Riggs wrote:
> During recovery procedures, there is a step that says
> 
> "If you didn't archive pg_xlog/ at all, then recreate it, and be sure to
> recreate the subdirectory pg_xlog/archive_status/ as well."
> 
> If you forget to do this, you may not realise until the recovering
> server comes up and tries writing to the directory. The message that is
> spat out when this happens is 
> 
> LOG:  could not create archive status file
> "pg_xlog/archive_status/00000001000003CE0000009E.ready": No such file or
> directory
> 
> We could check this just as the server comes up and then re-create it if
> necessary. So we have one less step in the process to remember. Existing
> scripts which perform this automatically will not need changing.
> 
> We can keep the message in case something removes the directory later.
> 
> Views?
> 
> -- 
>   Simon Riggs
>   2ndQuadrant  http://www.2ndQuadrant.com
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches
Next
From: Dave Cramer
Date:
Subject: Re: Request for feature - ECPGget_PGconn