Horton

Re: Error message inconsistency

Mahendra Singh Thalor <mahi6run@gmail.com>

View thread View on postgr.es
From: Mahendra Singh Thalor <mahi6run@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: MBeena Emerson <mbeena.emerson@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Fabrízio Mello <fabriziomello@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-22T07:39:58Z
Lists: pgsql-hackers 
On Tue, 21 Jan 2020 at 20:09, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
> On 2020-Jan-21, MBeena Emerson wrote:
>
> > The usage of the function errtableconstraint seems only to set the
> > schema_name table_name constraint_name internally and not for display
> > purposes. As seen in the following two cases where the relation name is
> > displayed using RelationGetRelationName and errtableconstraint is called as
> > part of errcode parameter not errmsg.
>
> You can see those fields by raising the log verbosity; it's a
> client-side thing. For example, in psql you can use
> \set VERBOSITY verbose
>
> In psql you can also use \errverbose after an error to print those
> fields.

Thanks for the explanation.

-- 
Thanks and Regards
Mahendra Singh Thalor
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Added relation name in error messages for constraint checks.