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

Re: [GENERAL] Regarding WAL

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Alexander Staubo" <alex(at)purefiction(dot)net>
Cc: "Mageshwaran" <j_mageshwaran(at)sifycorp(dot)com>,<pgsql-general(at)postgresql(dot)org>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: [GENERAL] Regarding WAL
Date: 2007-04-25 15:24:05
Message-ID: 1177514645.20637.143.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
On Tue, 2007-04-24 at 11:31 +0200, Alexander Staubo wrote:
> On 4/24/07, Mageshwaran <j_mageshwaran(at)sifycorp(dot)com> wrote:
> > I want to do replication using WAL , please tell the methods by which
> > log shipping is done ie moving the wal files to slaves and executing it.
> 
> Not possible at the moment: the log shipping facility that was
> introduced in 8.2 only lets you set up a so-called warm standby, which
> cannot be queried; it's not live replication.
> 
> The warm standby system is a fairly crude hack that relies on WAL
> files being copied from the main server to the standby and then
> starting the standby in recovery mode when you want to bring it up. At
> this point the standby is your main database, and it can no longer WAL
> files. Documented here:
> 
>  http://www.postgresql.org/docs/8.2/static/warm-standby.html

The use-case for Warm Standby is for people that want a simple,
efficient mechanism for providing High Availability replication.

If there are any feature requests, please let me know. 

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



In response to

pgsql-admin by date

Next:From: Pascal RobertDate: 2007-04-25 15:28:49
Subject: Finding time in WAL logs
Previous:From: Andrew DunstanDate: 2007-04-25 14:56:51
Subject: Re: [HACKERS] Kill a Long Running Query

pgsql-general by date

Next:From: Sergey KarinDate: 2007-04-25 15:25:46
Subject: FOREIGN KEY CONSTRAINT AND INHERITANCE
Previous:From: sangeetha k.sDate: 2007-04-25 15:13:22
Subject: reg: bitmap index implementation

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