Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Mar 10, 2015 at 1:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Another possibility is to leave it on through beta testing with the intent
>> to turn it off before 9.5 final; that would give us more data about
>> whether there are real issues than we're likely to get otherwise.
> To my mind, the fact that we're doing this at all is largely
> predicated on the fact that there won't be many real issues. So I
> think the goal of the debugging messages ought to be to let those
> people who discover that they do have issues track them down more
> easily, not to warn people. Warning is sort of closing the barn door
> after the horse has got out: hey, by the way, I just broke your app.
Agreed, but in the near term we need to *find out* whether there will
be many real issues. Perhaps having the warnings on by default would
help that, or perhaps not; I'm not sure.
> Another thing to consider is that if it becomes common to run with
> these warnings on, then everybody will have to pretty much write their
> code with full parenthesization anyway, at least if they plan to
> publish their code on PGXN or anywhere that it might get run on some
> system other than the one it was written for. That seems like an
> annoying gotcha for an issue that we're not expecting to be common.
Hm, well, people who are publishing code will likely want it to work
on both old and new PG releases, so I suspect they'd need to make it
run warning-free anyway.
regards, tom lane
