Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Robert Haas
Subject Re: max_standby_delay considered harmful
Date
Msg-id AANLkTimNx5bW0eTwcWUe079viqAQ9Sb5O-mdlMiZFb_v@mail.gmail.com
Whole thread Raw
In response to max_standby_delay considered harmful  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: max_standby_delay considered harmful
Re: max_standby_delay considered harmful
Re: max_standby_delay considered harmful
List pgsql-hackers
On Mon, May 3, 2010 at 11:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm inclined to think that we should throw away all this logic and just
> have the slave cancel competing queries if the replay process waits
> more than max_standby_delay seconds to acquire a lock.

What if we somehow get into a situation where the replay process is
waiting for a lock over and over and over again, because it keeps
killing conflicting processes but something restarts them and they
take locks over again?  It seems hard to ensure that replay will make
adequate progress with any substantially non-zero value of
max_standby_delay under this definition.

...Robert


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: max_standby_delay considered harmful
Next
From: Robert Haas
Date:
Subject: Re: Show schema in COPY error CONTEXT strings