pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: problem with WAL files
Date: Wed, 6 Jul 2005 19:00:44 -0400 (EDT)
Message-ID: <200507062300.j66N0ih09086@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.63.0507061543090.25488@discord.dyndns.org>

Jeff Frost wrote:
> On Thu, 30 Jun 2005, Tom Lane wrote:
> 
> > Jeff Frost <jeff@frostconsultingllc.com> writes:
> >> I'll have to retest that particular scenario and verify that something
> >> else was not causing the problem when I have a chance now that I have
> >> a fully functional and scripted out base backup and recover solution;
> >> however, it did not give me any of the errors I see when my
> >> walrestore.sh script cannot access an archived wal, so I would believe
> >> it did not even try to get it out of the archive.
> >
> 
> Tom,
> 
> Finally got a chance to give this another full test and discovered that the 
> WAL files work fine in the archive dir, but I uncovered a different problem. 
> What had happened was that when I rsynced the walarchive and walrestore 
> scripts over to the server, rsync made them mode 644 as they were in my cvs 
> sandbox and thus not executable.  When postgres went to call the script, I 
> guess it stat'd the walrestore, saw that it was not executable and quietly 
> reported that it could not find the WAL file in the pg_xlog dir.  Would 
> probably be handy to throw a warning that the restore command was not 
> executable, no?  Sorry for the false alarm before.

We basically run the command you give us via system(), so it is hard for
us to know exactly why it failed.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (12+ messages)  latest in thread

Message-ID: <200507062300.j66N0ih09086@candle.pha.pa.us>
Permalink:  ../200507062300.j66N0ih09086@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200507062300.j66N0ih09086@candle.pha.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pgman@candle.pha.pa.us, jeff@frostconsultingllc.com, tgl@sss.pgh.pa.us
  Subject: Re: problem with WAL files
  In-Reply-To: <200507062300.j66N0ih09086@candle.pha.pa.us>
  References: <Pine.LNX.4.63.0507061543090.25488@discord.dyndns.org> <200507062300.j66N0ih09086@candle.pha.pa.us>

* 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