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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Pascal Robert | 2007-04-25 15:28:49 | Finding time in WAL logs |
Previous Message | Andrew Dunstan | 2007-04-25 14:56:51 | Re: [HACKERS] Kill a Long Running Query |
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Karin | 2007-04-25 15:25:46 | FOREIGN KEY CONSTRAINT AND INHERITANCE |
Previous Message | sangeetha k.s | 2007-04-25 15:13:22 | reg: bitmap index implementation |