pgsql: Remove residual NULL-pstate handling in addRangeTableEntry.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove residual NULL-pstate handling in addRangeTableEntry.
Date: 2015-03-03 21:42:54
Message-ID: E1YSuac-0002lG-SU@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Remove residual NULL-pstate handling in addRangeTableEntry.

Passing a NULL pstate wouldn't actually work, because isLockedRefname()
isn't prepared to cope with it; and there hasn't been any in-core code
that tries in over a decade. So just remove the residual NULL handling.

Spotted by Coverity; analysis and patch by Michael Paquier.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5223ddacdc737b401ed58184e321f354bdf46686

Modified Files
--------------
src/backend/parser/parse_relation.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-03-04 02:19:47 pgsql: Fix long-obsolete code for separating filter conditions in cost_
Previous Message Alvaro Herrera 2015-03-03 17:18:56 pgsql: Change many routines to return ObjectAddress rather than OID