Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin. - Mailing list pgsql-committers

From Greg Stark
Subject Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.
Date
Msg-id 407d949e1001230933v649a2973pc59dfec14844c916@mail.gmail.com
Whole thread Raw
In response to pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.  (sriggs@postgresql.org (Simon Riggs))
Responses Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.
List pgsql-committers
On Sat, Jan 23, 2010 at 4:37 PM, Simon Riggs <sriggs@postgresql.org> wrote:
> max_standby_delay = -1 option removed to prevent deadlock.

This seems unacceptable to me. It means it's impossible to configure a
reporting slave so it doesn't spuriously signal errors if your reports
run too long.

Recall that I am still of the opinion that the only reasonable default
value for this parameter is actually -1. I don't think we should
signal errors for correctly working systems unless the user requests
them in some way.

Was there any discussion about this change? I don't recall seeing it
proposed on hackers.

--
greg

pgsql-committers by date:

Previous
From: sriggs@postgresql.org (Simon Riggs)
Date:
Subject: pgsql: Add explanatory detail to Hot Standby cancelation error messages
Next
From: Simon Riggs
Date:
Subject: Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.