Re: Feature Request: pg_replication_master()

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Robert Treat <rob(at)xzilla(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature Request: pg_replication_master()
Date: 2012-12-26 20:32:33
Message-ID: 50DB5EE1.7060208@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> There already are two ways to promote a server out of recovery. One is
> creating the trigger file. The other is "pg_ctl promote". (it uses a
> trigger file called $PGDATA/promote internally, but that's invisible to
> the user).

Right, I was thinking of the trigger file to put a server *into*
replication. That is, recovery.conf.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-12-26 20:33:59 json api WIP patch
Previous Message Heikki Linnakangas 2012-12-26 20:31:37 Re: Switching timeline over streaming replication