pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Zendel <alexzendel@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: question about wal and point in time recovery
Date: Wed, 13 Apr 2005 00:28:47 -0400
Message-ID: <3098.1113366527@sss.pgh.pa.us> (raw)
In-Reply-To: <BAY103-F4027A6F1BB965362B34C0FC3330@phx.gbl>
References: <BAY103-F4027A6F1BB965362B34C0FC3330@phx.gbl>

"Alex Zendel" <alexzendel@hotmail.com> 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



view thread (7+ messages)  latest in thread

Message-ID: <3098.1113366527@sss.pgh.pa.us>
Permalink:  ../3098.1113366527@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3098.1113366527@sss.pgh.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: tgl@sss.pgh.pa.us, alexzendel@hotmail.com
  Subject: Re: question about wal and point in time recovery
  In-Reply-To: <3098.1113366527@sss.pgh.pa.us>
  References: <BAY103-F4027A6F1BB965362B34C0FC3330@phx.gbl> <3098.1113366527@sss.pgh.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