pgsql: Change various deparsing functions to return NULL for invalid in - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Change various deparsing functions to return NULL for invalid in
Date
Msg-id E1bS8hg-0005Sg-3j@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Change various deparsing functions to return NULL for invalid input.

Previously, some functions returned various fixed strings and others
failed with a cache lookup error.  Per discussion, standardize on
returning NULL.  Although user-exposed "cache lookup failed" error
messages might normally qualify for bug-fix treatment, no back-patch;
the risk of breaking user code which is accustomed to the current
behavior seems too high.

Michael Paquier

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/976b24fb477464907737d28cdf18e202fa3b1a5b

Modified Files
--------------
src/backend/utils/adt/ruleutils.c   | 183 ++++++++++++++++++++++++++++--------
src/test/regress/expected/rules.out |  37 ++++++++
src/test/regress/sql/rules.sql      |   8 ++
3 files changed, 190 insertions(+), 38 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Repair damage done by citext--1.1--1.2.sql.
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql: doc: mention dependency on collation libraries