Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Robert Haas
Subject Re: max_standby_delay considered harmful
Date
Msg-id AANLkTiltf8sRCiSkrV6KpP7OD0ieLPZ3N-veWeIKW1Om@mail.gmail.com
Whole thread Raw
In response to Re: max_standby_delay considered harmful  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Wed, May 12, 2010 at 5:34 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Wed, 2010-05-12 at 14:43 -0400, Robert Haas wrote:
>
>> I thought that it
>> would be a good idea for Simon to look at it because, on the surface,
>> it APPEARS to have something to do with Hot Standby, since that's what
>> Stefan was testing when he found it.
>
> He was also testing SR, yet you haven't breathed a word about that for
> some strange reason. It didn't APPEAR like it was HS at all, not from
> basic logic or from technical knowledge. So you'll have to forgive me if
> I don't leap into action when you say something is an HS problem in the
> future.

Well, the original subject line of the report had mentioned SR only,
but I had a specific theory about what might be happening that was
related to the operation of HS.  You've said that you think my guess
is incorrect, and that's very possible, but until we actually find and
fix the bug we're all just guessing.  I wasn't intending to cast
aspersions on your code.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade versus MSVC build scripts
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade versus MSVC build scripts