Greetings, * Robert Haas (robertmh...@gmail.com) wrote: > On Mon, Aug 5, 2019 at 10:21 AM Stephen Frost <sfr...@snowman.net> wrote: > > Just to be clear, I brought up this exact concern back in *November*: > > > > https://www.postgresql.org/message-id/20181127153405.GX3415%40tamriel.snowman.net > > > > And now because this was pushed forward and the concerns that I raised > > ignored, we're having to deal with this towards the end of the release > > cycle instead of during normal development. > > I disagree.
It's unclear what you're disagreeing with here as the below response doesn't seem to discuss the question about if these issues were brought up and pointed out previously, nor about if I was the one who raised them, nor about if we're towards the end of the release cycle. > My analysis is that you're blocking a straightforward bug > fix because we're not prepared to redesign the world to match your > expectations. The actual point of controversy at the moment, as I > understand it, is this: if the backend, while rewriting > postgresql.auto.conf, discovers that it contains duplicates, should we > (a) give a WARNING or (b) not? No, that isn't the point of the controversy nor does it relate, at all, to what you quoted above, so I don't think there's much value in responding to the discussion about WARNING or not that you put together below. Thanks, Stephen
signature.asc
Description: PGP signature
