Re: question about wal and point in time recovery - Mailing list pgsql-admin

From Mohan, Ross
Subject Re: question about wal and point in time recovery
Date
Msg-id CC74E7E10A8A054798B6611BD1FEF4D307966B32@vamail01.thexchange.com
Whole thread Raw
In response to question about wal and point in time recovery  ("Alex Zendel" <alexzendel@hotmail.com>)
Responses Re: question about wal and point in time recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tom,

Is your (?) tool publically available?

<awkward pause>

Maybe I could have phrased that better....<sigh>


In any case, do you have a pointer to this R&R WAL tool?

Thanks,

Ross

-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Wednesday, April 13, 2005 12:29 AM
To: Alex Zendel
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] question about wal and point in time recovery


"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
contentsof 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
atall to make a change that would involve changing the size of a log entry.  So really the only useful option you have
hereis 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-agochange and not have that break some unknown number of consequent decisions. 

            regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

pgsql-admin by date:

Previous
From: Christopher Browne
Date:
Subject: Re: High Available Software Technologies Support About Postgres
Next
From: Tom Lane
Date:
Subject: Re: question about wal and point in time recovery