When on, the parser will emit a warning for any construct that might have changed meanings since PostgreSQL 9.4 as a result of changes in operator precedence. This is useful for auditing applications to see if precedence changes have broken anything; but it is not meant to be kept turned on in production, since it will warn about some perfectly valid, standard-compliant SQL code. The default is
See sql-precedence for more information.
- Postgresql going mad
- postgresql - too long select request
- Geoserver WFS + PostgreSQL with large table impossibly slow
- can't find the error in my postgresql.conf
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?