pgsql: Don't let transform_null_equals=on affect CASE foo WHEN NULL ...

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't let transform_null_equals=on affect CASE foo WHEN NULL ...
Date: 2011-10-08 08:33:29
Message-ID: E1RCSLZ-0007uY-1h@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't let transform_null_equals=on affect CASE foo WHEN NULL ... constructs.
transform_null_equals is only supposed to affect "foo = NULL" expressions
given directly by the user, not the internal "foo = NULL" expression
generated from CASE-WHEN.

This fixes bug #6242, reported by Sergey. Backpatch to all supported
branches.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/1ef60dab7049ffac52dee60b5788b6c7bc1f9d67

Modified Files
--------------
src/backend/parser/parse_expr.c | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Cédric Villemain 2011-10-08 10:40:03 Re: pgsql: Support index-only scans using the visibility map to avoid heap
Previous Message Heikki Linnakangas 2011-10-08 08:04:25 pgsql: Fix typo.