| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | urvancevav <urvancevav(at)gmail(dot)com> |
| Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #7574: CASE in WHERE condition change result set |
| Date: | 2012-10-02 03:59:10 |
| Message-ID: | 1349150280-sup-467@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from urvancevav's message of vie sep 28 05:58:42 -0300 2012:
> The following bug has been logged on the website:
>
> Bug reference: 7574
> Logged by: Andrei
> Email address: urvancevav(at)gmail(dot)com
> PostgreSQL version: 9.2.1
> Operating system: 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45
> Description:
>
> in query like this:
> [ snipped ]
> CASE operator in the WHERE condition actually sets clazz_ to 0 instead of
> filtering it.
Can you please provide a complete example? That would be something that
someone else can load into an empty database and observe the failure.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | nicwillemse | 2012-10-02 04:55:42 | BUG #7577: JDBC Driver - Compiled with Java 7 |
| Previous Message | Alvaro Herrera | 2012-10-02 03:50:42 | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |