Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 00153632A18 for ; Thu, 29 Jan 2009 21:22:13 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 47546-10 for ; Thu, 29 Jan 2009 21:22:10 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id C235A632487 for ; Thu, 29 Jan 2009 21:22:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n0U1M1SV014982; Thu, 29 Jan 2009 20:22:01 -0500 (EST) To: Lee Azzarello cc: pgsql-admin@postgresql.org Subject: Re: Warm standby recovery failure In-reply-to: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com> References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com> Comments: In-reply-to Lee Azzarello message dated "Thu, 29 Jan 2009 14:47:14 -0500" Date: Thu, 29 Jan 2009 20:22:01 -0500 Message-ID: <14981.1233278521@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/165 X-Sequence-Number: 31212 Lee Azzarello writes: > cp: writing `pg_xlog/./000000010000002F000000AA': No space left on device > 2009-01-29 12:48:14 UTC LOG: could not read from log file 47, segment > 170, offset 3129344: Success > 2009-01-29 12:48:14 UTC LOG: redo done at 2F/AA2FBE08 The bottom line here seems to be that your logfile transfer process passed a damaged (partial) WAL file to the slave postmaster, which interpreted the damage as being end of WAL. I'm not sure whether we could find a way to prevent it from doing that without causing bigger problems. In any case the most useful solution is going to involve fixing the transfer script so that it notices failures from 'cp' and doesn't pass the broken file on to the slave. We probably should add a caution about this to the manual's discussion of how to write archiving scripts. regards, tom lane