On 5 April 2018 at 21:00, Andres Freund <andres@anarazel.de> wrote:
> And if somebody cleans it up Simon will
> complain that things are needlessly being destabilized (hello xlog.c
> with it's 1000+ LOC functions).
Taking this comment as a special point... with other points addressed
separately.
...If anybody wants to know what I think they can just ask...
There are various parts of the code that don't have full test
coverage. Changing things there is more dangerous and if its being
done for no reason then that is risk for little reward. That doesn't
block it, but it does make me think that people could spend their time
better - and issue that concerns me also.
But that certainly doesn't apply to parts of the code like this where
we have full test coverage.
It may not even apply to recovery now we have the ability to check in
real-time the results of recovery and replication.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
