pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kailash Vyas <kailash.vyas@gmail.com>
To: pgsql-admin@postgresql.org
Cc: thomas.revell@powerconv.alstom.com <thomas.revell@powerconv.alstom.com>
Subject: Re: wal logging
Date: Fri, 17 Jun 2005 14:09:53 +0100
Message-ID: <a3cc79170506170609580f1ad0@mail.gmail.com> (raw)
In-Reply-To: <OFB7D0D8D0.3CF355CD-ON80257023.003EDC8D-80257023.00400944@test.alstom.com>
References: <OFB7D0D8D0.3CF355CD-ON80257023.003EDC8D-80257023.00400944@test.alstom.com>

thanks for the info.
what is the utility of WAL logging in postgres 7.3 

thanks,
kailash

On 6/17/05, thomas.revell@powerconv.alstom.com <
thomas.revell@powerconv.alstom.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@postgresql.org so that your
> message can get through to the mailing list cleanly
>

view thread (7+ messages)  latest in thread

Message-ID: <a3cc79170506170609580f1ad0@mail.gmail.com>
Permalink:  ../a3cc79170506170609580f1ad0@mail.gmail.com/
Also on:    postgresql.org/message-id/a3cc79170506170609580f1ad0@mail.gmail.com

 · 

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: kailash.vyas@gmail.com, thomas.revell@powerconv.alstom.com
  Subject: Re: wal logging
  In-Reply-To: <a3cc79170506170609580f1ad0@mail.gmail.com>
  References: <OFB7D0D8D0.3CF355CD-ON80257023.003EDC8D-80257023.00400944@test.alstom.com> <a3cc79170506170609580f1ad0@mail.gmail.com>

* 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