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

Re: [HACKERS] Hot Standby utility and administrator functions

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, pgadmin-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [HACKERS] Hot Standby utility and administrator functions
Date: 2008-10-27 16:12:18
Message-ID: 1225123938.3971.20.camel@ebony.2ndQuadrant (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackerspgsql-generalpgsql-hackers
On Mon, 2008-10-27 at 11:42 -0400, Robert Treat wrote:

> On Monday 20 October 2008 05:25:29 Simon Riggs wrote:
> > I'm looking to implement the following functions for Hot Standby, to
> > allow those with administrative tools or management applications to have
> > more control during recovery. Please let me know if other functions are
> > required.
> >
> > What else do we need?
> >
> Is it possible to give the master/slave knowledge about each other?

Yes, but for what reason?

The project I'm working on is Hot Standby, not streaming replication.
That will link things together better than they are now, so I'd probably
rather not prejudge/duplicate that.

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-hackers by date

Next:From: Hitoshi HaradaDate: 2008-10-27 16:12:22
Subject: Window Functions: v07 APIs and buffering strateties
Previous:From: Webb SpragueDate: 2008-10-27 16:11:12
Subject: Website request -- developer docs along with release docs

pgadmin-hackers by date

Next:From: Emmanuel CecchetDate: 2008-10-27 16:53:37
Subject: Re: [HACKERS] Hot Standby utility and administrator functions
Previous:From: Robert TreatDate: 2008-10-27 15:42:47
Subject: Re: [HACKERS] Hot Standby utility and administrator functions

pgsql-general by date

Next:From: David BrainDate: 2008-10-27 16:30:08
Subject: EXECUTE in trigger functions.
Previous:From: Steve ClarkDate: 2008-10-27 16:10:25
Subject: Re: 8.3.x log maintenance

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