Skip site navigation (1) Skip section navigation (2)

Re: wal logging

From: Kailash Vyas <kailash(dot)vyas(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Cc: "thomas(dot)revell(at)powerconv(dot)alstom(dot)com" <thomas(dot)revell(at)powerconv(dot)alstom(dot)com>
Subject: Re: wal logging
Date: 2005-06-17 13:09:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
thanks for the info.
what is the utility of WAL logging in postgres 7.3 


On 6/17/05, thomas(dot)revell(at)powerconv(dot)alstom(dot)com <
thomas(dot)revell(at)powerconv(dot)alstom(dot)com> wrote:
> Database recovery from write ahead logs is only supported in PostgreSQL
> 8.0.0 and later.
> -----------------------------------------------------------------------
> hi
> I have to setup some backup policies for our postgres server.
> I had a few queries regarding corruption of database.
> what are the steps to be followed in postgres regarding logical
> corruption, instance failures, block corruption, log corruption?
> I am using postgres 7.3.9
> I was checking out WAL logging. I enabled WAL logging in postgres.conf
> I found the logs in the pg_xlog directory but don't know how to recover it
> thanks,
> kailash
> :.________________
> CONFIDENTIALITY : This e-mail and any attachments are confidential and
> may be privileged. If you are not a named recipient, please notify the
> sender immediately and do not disclose the contents to another person, use
> it for any purpose or store or copy the information in any medium.
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

In response to


pgsql-admin by date

Next:From: Bruce MomjianDate: 2005-06-17 13:21:20
Subject: Re: FATAL: invalid value for parameter "wal_sync_method":
Previous:From: thomas.revellDate: 2005-06-17 11:28:31
Subject: Re: wal logging

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group