pgsql: Improve some error wording with multirange type parsing

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Improve some error wording with multirange type parsing
Date: 2021-05-31 02:35:35
Message-ID: E1lnXmB-0001Vs-Gf@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve some error wording with multirange type parsing

Braces were referred in some error messages as only brackets (not curly
brackets or curly braces), which can be confusing as other types of
brackets could be used.

While on it, add one test to check after the case of junk characters
detected after a right brace.

Author: Kyotaro Horiguchi
Discussion: https://postgr.es/m/20210514.153153.1814935914483287479.horikyota.ntt@gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/12cc956664f159e97be71e33f15ec5f42e46b24e

Modified Files
--------------
src/backend/utils/adt/multirangetypes.c | 4 ++--
src/test/regress/expected/multirangetypes.out | 7 ++++++-
src/test/regress/sql/multirangetypes.sql | 1 +
3 files changed, 9 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2021-05-31 07:33:55 pgsql: Raise a timeout to 180s, in test 010_logical_decoding_timelines.
Previous Message Tom Lane 2021-05-29 18:27:43 pgsql: Doc: improve libpq service-file docs, avoid overspecifying pathn