Re: Hot Standby and handling max_standby_delay - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hot Standby and handling max_standby_delay
Date
Msg-id 18899.1263659822@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hot Standby and handling max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standby and handling max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> I'm wondering if it wouldn't just be easier to put in a plugin for
> recovery conflict handling, so the user can decide what to do
> themselves. That seems like a better plan than chewing through these
> issues now. 

Making it a plugin doesn't solve anything.  This is not the kind of
thing where people can come up with some random policy and it will
work well.  Anyone competent to invent a better policy would be quite
capable of modifying the source to suit themselves.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Standby and handling max_standby_delay
Next
From: Stefan Kaltenbrunner
Date:
Subject: buildfarm compiler warnings