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

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Require non-NULL pstate for all addRangeTableEntryFor* functions
Date: 2015-03-11 19:36:03
Message-ID: E1YVmQF-00088A-Vc@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2015-03-11 19:48:57 pgsql: PL/Python: Avoid lossiness in float conversion
Previous Message Tom Lane 2015-03-11 17:22:58 pgsql: Make operator precedence follow the SQL standard more closely.