Re: Removal of operator_precedence_warning

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Removal of operator_precedence_warning
Date: 2020-12-04 22:01:38
Message-ID: 20201204220138.GA955@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2020-Dec-04, Tom Lane wrote:

> I think it's time for $SUBJECT. We added this GUC in 9.5, which
> will be EOL by the time of our next major release, and it was never
> meant as more than a transitional aid. Moreover, it's been buggy
> as heck (cf abb164655, 05104f693, 01e0cbc4f, 4cae471d1), and the
> fact that some of those errors went undetected for years shows that
> it's not really gotten much field usage.
> Hence, I propose the attached. Comments?

I wonder if it'd be fruitful to ask the submitters of those bugs about
their experiences with the feature. Did they find it useful in finding
precedence problems in their code? Did they experience other problems
that they didn't report?

Reading the reports mentioned in those commits, it doesn't look like any
of them were actually using the feature -- they all seem to have come
across the problems by accidents of varying nature.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2020-12-04 22:17:39 Re: A few new options for CHECKPOINT
Previous Message Peter Geoghegan 2020-12-04 22:00:48 Re: POC: Better infrastructure for automated testing of concurrency issues