| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgsql-general pgsql-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 www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emmanuel Cecchet | 2008-10-27 16:53:37 | Re: [HACKERS] Hot Standby utility and administrator functions |
| Previous Message | Robert Treat | 2008-10-27 15:42:47 | Re: [HACKERS] Hot Standby utility and administrator functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Brain | 2008-10-27 16:30:08 | EXECUTE in trigger functions. |
| Previous Message | Steve Clark | 2008-10-27 16:10:25 | Re: 8.3.x log maintenance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2008-10-27 16:12:22 | Window Functions: v07 APIs and buffering strateties |
| Previous Message | Webb Sprague | 2008-10-27 16:11:12 | Website request -- developer docs along with release docs |