Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: max_standby_delay considered harmful
Date
Msg-id m2tyql86kq.fsf@hi-media.com
Whole thread Raw
In response to Re: max_standby_delay considered harmful  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: max_standby_delay considered harmful
Re: max_standby_delay considered harmful
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> It would be easier to implement a conflict resolution plugin that is
> called when a conflict occurs, allowing users to have a customisable
> mechanism. Again, I have no objection to that proposal.

To implement, if you say so, no doubt. To use, that means you need to
install a contrib module after validation that the trade offs there are
the one you're interested into, or you have to code it yourself. In C.

I don't see that as an improvement over what we have now. Our main
problem seems to be the documentation of the max_standby_delay, where we
give the impression it's doing things the code can not do. IIUC.

Regards,
-- 
dim


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: SQLSTATE for Hot Standby cancellation
Next
From: Mike Fowler
Date:
Subject: Adding xpath_exists function