pgsql: Remove residual NULL-pstate handling in addRangeTableEntry. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Remove residual NULL-pstate handling in addRangeTableEntry.
Date
Msg-id E1YSuac-0002lG-SU@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: Change many routines to return ObjectAddress rather than OID
Next
From: Tom Lane
Date:
Subject: pgsql: Fix long-obsolete code for separating filter conditions in cost_