Re: Make INFO messages consistent in various index *validate() functions

From: Neha Khatri <nehakhatri5(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Make INFO messages consistent in various index *validate() functions
Date: 2017-02-27 01:53:15
Message-ID: CAFO0U+-q3uy1oB7wzko+Rj9CRYPWZghaCKL+UfDo169vKsex_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Mon, Feb 27, 2017 at 12:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> neha khatri <nehakhatri5(at)gmail(dot)com> writes:
> > Does the community believe that the existing INFO message, as shown
> below,
> > is clear enough for the users.
> > "btree operator family "bpchar_ops" contains function
> > bpcharcmp(character,character) with wrong signature for support number 1"
>
> Well, that message is targeted at somebody who's built a btree operator
> class and is testing it, so I should think it would be clear enough to
> them.

Sure, that clarifies.

Thanks.
Neha

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Neha Khatri 2017-03-07 04:54:31 opr_charset rule in gram.y
Previous Message Tom Lane 2017-02-27 01:03:48 Re: Make INFO messages consistent in various index *validate() functions