pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
wal logging
7+ messages / 5 participants
[nested] [flat]

* wal logging
@ 2005-06-17 11:09 Kailash Vyas <kailash.vyas@gmail.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Kailash Vyas @ 2005-06-17 11:09 UTC (permalink / raw)
  To: pgsql-admin

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

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
@ 2005-06-17 11:28 thomas.revell@powerconv.alstom.com
  2005-06-17 13:09 ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
  0 siblings, 1 reply; 7+ messages in thread

From: thomas.revell@powerconv.alstom.com @ 2005-06-17 11:28 UTC (permalink / raw)
  To: pgsql-admin

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.



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
  2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
@ 2005-06-17 13:09 ` Kailash Vyas <kailash.vyas@gmail.com>
  2005-06-17 14:00   ` Re: wal logging Tom Lane <tgl@sss.pgh.pa.us>
  2005-06-17 19:52   ` Re: wal logging Bruno Wolff III <bruno@wolff.to>
  0 siblings, 2 replies; 7+ messages in thread

From: Kailash Vyas @ 2005-06-17 13:09 UTC (permalink / raw)
  To: pgsql-admin; +Cc: thomas.revell@powerconv.alstom.com <thomas.revell@powerconv.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
>

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
  2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
  2005-06-17 13:09 ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
@ 2005-06-17 14:00   ` Tom Lane <tgl@sss.pgh.pa.us>
  2005-06-17 15:08     ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
  1 sibling, 1 reply; 7+ messages in thread

From: Tom Lane @ 2005-06-17 14:00 UTC (permalink / raw)
  To: Kailash Vyas <kailash.vyas@gmail.com>; +Cc: pgsql-admin@postgresql.org, "thomas.revell@powerconv.alstom.com" <thomas.revell@powerconv.alstom.com>

Kailash Vyas <kailash.vyas@gmail.com> writes:
> what is the utility of WAL logging in postgres 7.3

Crash protection.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
  2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
  2005-06-17 13:09 ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
  2005-06-17 14:00   ` Re: wal logging Tom Lane <tgl@sss.pgh.pa.us>
@ 2005-06-17 15:08     ` Kailash Vyas <kailash.vyas@gmail.com>
  2005-06-17 15:23       ` Re: wal logging hubert depesz lubaczewski <depesz@gmail.com>
  0 siblings, 1 reply; 7+ messages in thread

From: Kailash Vyas @ 2005-06-17 15:08 UTC (permalink / raw)
  To: pgsql-admin; +Cc: Tom Lane <tgl@sss.pgh.pa.us>

thanks tom for you prompt response.
can you give me more info into crash protection.
for example in case of database crash what would be the steps involved in 
recovering it through WAL.

thanks,
kailash

On 6/17/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Kailash Vyas <kailash.vyas@gmail.com> writes:
> > what is the utility of WAL logging in postgres 7.3
> 
> Crash protection.
> 
> regards, tom lane
>

^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
  2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
  2005-06-17 13:09 ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
  2005-06-17 14:00   ` Re: wal logging Tom Lane <tgl@sss.pgh.pa.us>
  2005-06-17 15:08     ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
@ 2005-06-17 15:23       ` hubert depesz lubaczewski <depesz@gmail.com>
  0 siblings, 0 replies; 7+ messages in thread

From: hubert depesz lubaczewski @ 2005-06-17 15:23 UTC (permalink / raw)
  To: Kailash Vyas <kailash.vyas@gmail.com>; +Cc: pgsql-admin

On 6/17/05, Kailash Vyas <kailash.vyas@gmail.com> wrote:
>  for example in case of database crash what would be the steps involved in
> recovering it through WAL.

just restart the database.
postgresql with recover itself using wal files.

depesz



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: wal logging
  2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
  2005-06-17 13:09 ` Re: wal logging Kailash Vyas <kailash.vyas@gmail.com>
@ 2005-06-17 19:52   ` Bruno Wolff III <bruno@wolff.to>
  1 sibling, 0 replies; 7+ messages in thread

From: Bruno Wolff III @ 2005-06-17 19:52 UTC (permalink / raw)
  To: Kailash Vyas <kailash.vyas@gmail.com>; +Cc: pgsql-admin@postgresql.org, "thomas.revell@powerconv.alstom.com" <thomas.revell@powerconv.alstom.com>

On Fri, Jun 17, 2005 at 14:09:53 +0100,
  Kailash Vyas <kailash.vyas@gmail.com> wrote:
> thanks for the info.
> what is the utility of WAL logging in postgres 7.3 

It allows the postres to recover if the server crashes.



^ permalink  raw  reply  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2005-06-17 19:52 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-06-17 11:09 wal logging Kailash Vyas <kailash.vyas@gmail.com>
2005-06-17 11:28 Re: wal logging thomas.revell@powerconv.alstom.com
2005-06-17 13:09 ` Kailash Vyas <kailash.vyas@gmail.com>
2005-06-17 14:00   ` Tom Lane <tgl@sss.pgh.pa.us>
2005-06-17 15:08     ` Kailash Vyas <kailash.vyas@gmail.com>
2005-06-17 15:23       ` hubert depesz lubaczewski <depesz@gmail.com>
2005-06-17 19:52   ` Bruno Wolff III <bruno@wolff.to>

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