pgsql: Always initialize PartitionBoundInfoData's null_index.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Always initialize PartitionBoundInfoData's null_index.
Date: 2017-06-13 16:41:13
Message-ID: E1dKosT-0002NJ-Rf@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Always initialize PartitionBoundInfoData's null_index.

This doesn't actually matter at present, because the current code
never consults null_index for range partitions. However, leaving
it uninitialized is still a bad idea, so let's not do that.

Amul Sul, reviewed by Ashutosh Bapat

Discussion: http://postgr.es/m/CAAJ_b94AkEzcx+12ySCnbMDX7=UdF4BjnoBGfMQbB0RNSTo3Ng@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/096f1ccd5290286b135822bb282fa884454d4b69

Modified Files
--------------
src/backend/catalog/partition.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-06-13 17:06:11 pgsql: Re-run pgindent.
Previous Message Dean Rasheed 2017-06-13 16:33:16 pgsql: Teach relation_is_updatable() about partitioned tables.