Re: WIP: Failover Slots - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP: Failover Slots
Date
Msg-id CA+TgmoZam8QYYsP=u44pQiF+wqMVzWZrTsYWvQ_Okju65SsxxQ@mail.gmail.com
Whole thread Raw
In response to WIP: Failover Slots  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: WIP: Failover Slots  (Simon Riggs <simon@2ndQuadrant.com>)
Re: WIP: Failover Slots  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Fri, Jan 1, 2016 at 7:50 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Failover Slots
> In the current patch, any slot defined on a master will generate WAL,
> leading to a pending-slot being present on all standby nodes. When a standby
> is promoted, the slot becomes usable and will have the properties as of the
> last fsync on the master.

No objection to the concept, but I think the new behavior needs to be
optional.  I am guessing that you are thinking along similar lines,
but it's not explicitly called out here.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: removal of unused argument in ginInsertCleanup()
Next
From: Robert Haas
Date:
Subject: Re: Set search_path + server-prepared statements = cached plan must not change result type