Re: Error message inconsistency - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Error message inconsistency
Date
Msg-id CAA4eK1KnBBi4HMmXcYT+_MSNRJfVHG75Ck2pZrVg-XevunxnHQ@mail.gmail.com
Whole thread Raw
In response to Re: Error message inconsistency  (MBeena Emerson <mbeena.emerson@gmail.com>)
Responses Re: Error message inconsistency  (MBeena Emerson <mbeena.emerson@gmail.com>)
List pgsql-hackers
On Thu, Jan 9, 2020 at 5:42 PM MBeena Emerson <mbeena.emerson@gmail.com> wrote:
>

Hi Beena,

It is better to reply inline.

> Hi Mahendra,
>
> Thanks for the patch.
> I am not sure but maybe the relation name should also be added to the following test case?
>
> create table t4 (id int);
> insert into t4 values (1);
> ALTER TABLE t4 ADD CONSTRAINT c1 CHECK (id > 10) NOT VALID; -- succeeds
> ALTER TABLE t4 VALIDATE CONSTRAINT c1;
> ERROR:  check constraint "c1" is violated by some row
>

I see that in this case, we are using errtableconstraint which should
set table/schema name, but then that doesn't seem to be used.  Can we
explore it a bit from that angle?

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Option to dump foreign data in pg_dump
Next
From: Thomas Munro
Date:
Subject: Re: [PATCH] Resolve Parallel Hash Join Performance Issue