X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E4A0052838 for ; Wed, 6 Jul 2005 20:00:58 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02410-05 for ; Wed, 6 Jul 2005 23:00:49 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126]) by svr1.postgresql.org (Postfix) with ESMTP id 929FA529A1 for ; Wed, 6 Jul 2005 20:00:43 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id j66N0ih09086; Wed, 6 Jul 2005 19:00:44 -0400 (EDT) From: Bruce Momjian Message-Id: <200507062300.j66N0ih09086@candle.pha.pa.us> Subject: Re: problem with WAL files In-Reply-To: To: Jeff Frost Date: Wed, 6 Jul 2005 19:00:44 -0400 (EDT) Cc: Tom Lane , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/40 X-Sequence-Number: 18096 Jeff Frost wrote: > On Thu, 30 Jun 2005, Tom Lane wrote: > > > Jeff Frost 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