Re: High Availability PostgreSQL HOWTO article

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: High Availability PostgreSQL HOWTO article
Date: 2002-08-06 21:49:40
Message-ID: 20020806174940.D29630@mail.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Aug 06, 2002 at 03:42:19PM -0400, Robert M. Meyer wrote:

> I've been thinking about the debug flags that allow me to log all of the
> queries that pass through the system as a possible path to this. It
> wouldn't be hard to write a perl/sed/awk/whatever script to strip out
> the 'DEBUG:' bits and removes the 'SELECT' queries, leaving only the
> 'UPDATE' and 'INSERT' queries. This could be trapped by a process that
> writes out the stream to a process on the replica server that would just
> store them in a file. In the event of a primary system failure, a
> process would detect the loss of the primary server, force the current
> transaction log into the database, turn off the receiver daemon, then
> take whatever actions are necessary to become the primary.

Sounds like what you want is replication via a replay of the WAL.
Maybe take the work currently being done on PITR (over on -hackers)
and try to extend it?

A

--
----
Andrew Sullivan 87 Mowat Avenue
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M6K 3E3
+1 416 646 3304 x110

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Chad R. Larson 2002-08-06 22:00:17 Re: Automated database backups and authentication
Previous Message Artur Pietruk 2002-08-06 21:34:58 Re: Automated database backups and authentication