From: | neha khatri <nehakhatri5(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Make INFO messages consistent in various index *validate() functions |
Date: | 2017-02-24 03:24:39 |
Message-ID: | CAFO0U+--_R5S18NKESomYfN7NxwmaL3KGSnS+85SEe7+vkKFfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi,
While experimenting with operator class support functions I saw following
INFO message generated by nbtvalidate():
btree operator family "bpchar_ops" contains function
bpcharcmp(character,character) with wrong signature for support number 1
The 'support number 1' above looks somewhat raw. Some of the other INFO
messages in other index validate function(ginvalidate, gistvalidate) use
the term "support procedure" or "support function".
gin operator class \"%s\" is missing support function %d
This message seems to use friendlier term. In fact the number is actually
for a Support Procedure.
Probably the first message above, when restructured as shown below, might
be more friendlier:
btree operator family "bpchar_ops" contains function
bpcharcmp(character,character) as support procedure 1, with wrong signature
Would it be worth an effort to make these messages consistent and more user
friendly.
Regards,
Neha
From | Date | Subject | |
---|---|---|---|
Next Message | neha khatri | 2017-02-26 22:01:28 | Re: Make INFO messages consistent in various index *validate() functions |
Previous Message | KARIN SUSANNE HILBERT | 2017-02-23 11:12:30 | Re: Create PostgreSQL Database with ENCODING 'WIN1252' on Cluster Initialized with locale "en_US.UTF-8"? |