pgsql: Fix improper NULL handling in list partitioning code.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix improper NULL handling in list partitioning code.
Date: 2017-03-27 14:54:56
Message-ID: E1csW2q-0006wi-Ga@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix improper NULL handling in list partitioning code.

The previous logic was wrong when the value was NULL but there was
no partition for NULL.

Amit Langote, reviewed by Jeevan Ladhe

Discussion: http://postgr.es/m/d64f8498-70eb-3c88-b56d-c54fd3b0500f@lab.ntt.co.jp

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/7ecb7143589f38d679bb566311dfa9be1a650fd5

Modified Files
--------------
src/backend/catalog/partition.c | 10 +++++++---
src/test/regress/expected/insert.out | 7 +++++++
src/test/regress/sql/insert.sql | 6 ++++++
3 files changed, 20 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-03-27 15:00:25 pgsql: Tidy up the CREATE TABLE documentation for partitioning.
Previous Message Robert Haas 2017-03-27 14:39:59 pgsql: Allow ON CONFLICT .. DO NOTHING on a partitioned table.