From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Precedence of standard comparison operators |
Date: | 2015-03-10 19:13:23 |
Message-ID: | 1391.1426014803@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> On Tue, Mar 10, 2015 at 10:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This thread seems to have died off without any clear resolution. I'd
>> hoped somebody would try the patch on some nontrivial application to
>> see if it broke anything or caused any warnings, but it doesn't seem
>> like that is happening.
> I tried it on a fairly typical web application. Around 5000 or so distinct
> statements according to pg_stat_statements. With
> operator_precedence_warning = on, no warnings yet.
Thanks! Much appreciated.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-03-10 19:31:52 | Re: Parallel Seq Scan |
Previous Message | Alex Hunsaker | 2015-03-10 19:10:03 | Re: Precedence of standard comparison operators |