| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | MBeena Emerson <mbeena(dot)emerson(at)gmail(dot)com> |
| Cc: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Error message inconsistency |
| Date: | 2020-01-21 05:19:46 |
| Message-ID: | CAA4eK1KnBBi4HMmXcYT+_MSNRJfVHG75Ck2pZrVg-XevunxnHQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 9, 2020 at 5:42 PM MBeena Emerson <mbeena(dot)emerson(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-01-21 05:20:11 | Re: [PATCH] Resolve Parallel Hash Join Performance Issue |
| Previous Message | vignesh C | 2020-01-21 05:16:29 | Re: Option to dump foreign data in pg_dump |