Re: Incorrectly reporting config errors

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> The only real argument for the message:

> LOG: configuration file "/home/thom/Development/data/postgresql.conf"
> contains errors; unaffected changes were applied

> ...is that somebody might think that the presence of a single error
> caused all the changes to be ignored. And there's a good reason they
> might think that: we used to do it that way. But on the flip side, if
> we emitted a LOG or WARNING message every time the user did something
> that works in a way incompatible with previous releases, we'd go
> insane. So I think the argument for just dumping that message
> altogether is actually pretty good.

Hm. I don't recall what the arguments were for adding that message,
but you have a point that it might have served its purpose by now.

regards, tom lane