pgsql: Require non-NULL pstate for all addRangeTableEntryFor* functions - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Require non-NULL pstate for all addRangeTableEntryFor* functions
Date
Msg-id E1YVmQF-00088A-Vc@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Require non-NULL pstate for all addRangeTableEntryFor* functions.

Per discussion, it's better to have a consistent coding rule here.

Michael Paquier, per a node from Greg Stark referencing an old post
from Tom Lane.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/bc93ac12c2544b6b3a68b6cb0282e0828fa14a34

Modified Files
--------------
src/backend/commands/view.c            |    8 ++++++--
src/backend/optimizer/plan/subselect.c |    6 +++++-
src/backend/parser/parse_relation.c    |   30 ++++++++++++++++++------------
3 files changed, 29 insertions(+), 15 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Make operator precedence follow the SQL standard more closely.
Next
From: Peter Eisentraut
Date:
Subject: pgsql: PL/Python: Avoid lossiness in float conversion