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 360B053B27 for ; Wed, 13 Apr 2005 01:28:51 -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 75642-09 for ; Wed, 13 Apr 2005 04:28:50 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E5EAC53B42 for ; Wed, 13 Apr 2005 01:28:49 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3D4SmrW003099; Wed, 13 Apr 2005 00:28:48 -0400 (EDT) To: "Alex Zendel" Cc: pgsql-admin@postgresql.org Subject: Re: question about wal and point in time recovery In-reply-to: References: Comments: In-reply-to "Alex Zendel" message dated "Tue, 12 Apr 2005 07:47:27 -0600" Date: Wed, 13 Apr 2005 00:28:47 -0400 Message-ID: <3098.1113366527@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/168 X-Sequence-Number: 17181 "Alex Zendel" writes: > ... i've been reading up on the wal and point in time recovery in > the online postgre manual. but i have a question about using it: [ obligatory gripe: it's postgres or postgresql, not postgre ] > is it possible to visually read the entries in the log? Not readily. If you find yourself backed into a corner, I have a rough-and-ready debug tool for printing out the contents of a WAL log, but I'd surely not want to call it "supported" in its current form... > can the log be modified before recovery occurs. Not easily. If you were to hack any one log entry, you'd have to recompute the CRC checksum for it, and there's no way at all to make a change that would involve changing the size of a log entry. So really the only useful option you have here is to stop recovery short of a particular log entry you don't like. > my biggest concern is that somebody in my org, for example, deletes a > field or fudges an update query that changes a foreign key to a single > value - and therefore destroys table links. so what if this happens > and nobody notices it for several weeks? There is no automatic recovery mechanism that is going to help you in such a scenario. You can't expect to undo a long-ago change and not have that break some unknown number of consequent decisions. regards, tom lane