Re: Error message inconsistency
От | Mahendra Singh Thalor |
---|---|
Тема | Re: Error message inconsistency |
Дата | |
Msg-id | CAKYtNApE8GhC7+Bg4wMSHXCCA2F=QwsLAM9wfCoDSOFCBZLvmg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Error message inconsistency (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Список | 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
В списке pgsql-hackers по дате отправления: