Re: Sync Rep v19

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sync Rep v19
Date: 2011-03-05 17:59:50
Message-ID: AANLkTikfk9FfzHas1P0A1rK06gfSmseQbfHmkkzCth7d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 5, 2011 at 11:56 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Even though postmaster dies, the waiting backend keeps waiting until
>> the timeout expires. Instead, the backends should periodically check
>> whether postmaster is alive, and then they should exit immediately
>> if it's not alive, as well as other process does? If the timeout is
>> disabled, such backends would get stuck infinitely.
>
> Will wake them every 60 seconds

I don't really see why sync rep should be responsible for solving this
problem, which is an issue in many other situations as well, only for
itself. In fact I think I'd prefer that it didn't, and that we wait
for a more general solution that will actually fix this problem for
real.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-05 18:02:50 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Previous Message Andres Freund 2011-03-05 17:55:41 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)