[Pacemaker] PGSQL resource promotion issue

[Steven Bambling]

On Mar 28, 2013, at 8:13 AM, Rainer Brestan <rainer.brestan at gmx.net<mailto:rainer.brestan at gmx.net>> wrote:

Hi Steve,
i think, you have misunderstood how ip addresses are used with this setup, PGVIP should start after promotion.
Take a look at Takatoshi´s Wiki.
https://github.com/t-matsuo/resource-agents/wiki/Resource-Agent-for-PostgreSQL-9.1-streaming-replication

I see that he has the master/replication VIPs with a resource order to force promotion before moving the VIPs to the new master.

  I don't get how the postgres service is going to listen on those interfaces if they have not already migrated to the new master.  Even with setting the listen_addresses = "*"


The promotion sequency is very simple.
When no master is existing, all slaves write their current replay xlog into the node attribute PGSQL-xlog-loc during monitor call.
Does this also hold true if a Master fails?