On Wed, May 25, 2011 at 11:07 PM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> On 25.05.2011 07:42, Fujii Masao wrote:
>>> To achieve that, I'm thinking to change walsender so that, when the standby
>>> has caught up with the master, it sends back the message indicating that to
>>> the standby
On Wed, May 25, 2011 at 3:11 PM, Jaime Casanova wrote:
> On Wed, May 25, 2011 at 12:28 AM, Fujii Masao wrote:
>> On Wed, May 25, 2011 at 2:16 PM, Heikki Linnakangas
>>> By the time the standby has received that message, it might not be caught-up
>>> anymore because new WAL might've been generated
On Wed, May 25, 2011 at 12:34:59PM +0100, Simon Riggs wrote:
> On Wed, May 25, 2011 at 6:16 AM, Heikki Linnakangas
> wrote:
>
> >> To achieve that, I'm thinking to change walsender so that, when the
> >> standby
> >> has caught up with the master, it sends back the message indicating that
> >> to
Heikki Linnakangas writes:
> On 25.05.2011 07:42, Fujii Masao wrote:
>> To achieve that, I'm thinking to change walsender so that, when the standby
>> has caught up with the master, it sends back the message indicating that to
>> the standby. And I'm thinking to add new function (or view like
>> p
On Wed, May 25, 2011 at 6:16 AM, Heikki Linnakangas
wrote:
>> To achieve that, I'm thinking to change walsender so that, when the
>> standby
>> has caught up with the master, it sends back the message indicating that
>> to
>> the standby. And I'm thinking to add new function (or view like
>> pg_s
On Wed, May 25, 2011 at 12:28 AM, Fujii Masao wrote:
> On Wed, May 25, 2011 at 2:16 PM, Heikki Linnakangas
>>>
>>> To achieve that, I'm thinking to change walsender so that, when the
>>> standby
>>> has caught up with the master, it sends back the message indicating that
>>> to
>>> the standby. An
On Wed, May 25, 2011 at 2:16 PM, Heikki Linnakangas
wrote:
> On 25.05.2011 07:42, Fujii Masao wrote:
>>
>> For reliable high-availability, when the master crashes, the clusterware
>> must
>> know whether it can promote the standby safely without any data loss,
>> before actually promoting it. IOW,
On 25.05.2011 07:42, Fujii Masao wrote:
For reliable high-availability, when the master crashes, the clusterware must
know whether it can promote the standby safely without any data loss,
before actually promoting it. IOW, it must know whether the standby has
already caught up with the primary. O
Hi,
For reliable high-availability, when the master crashes, the clusterware must
know whether it can promote the standby safely without any data loss,
before actually promoting it. IOW, it must know whether the standby has
already caught up with the primary. Otherwise, failover might cause data l