| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "goodluck(dot)deep989(at)gmail(dot)com" <goodluck(dot)deep989(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bug : Did't show Constaint violation error |
| Date: | 2021-03-01 01:34:55 |
| Message-ID: | 663313.1614562495@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sunday, February 28, 2021, <goodluck(dot)deep989(at)gmail(dot)com> wrote:
>> I think it should not allow to add this constraint if we have the column
>> char size is less than the size of values on which we are putting the
>> constraints.
> It doesn’t seem worth the effort.
Even more to the point, it'd probably be a violation of the SQL standard.
The standard does not prohibit unsatisfiable constraints. (IIRC, people
actually use such things, too, if they want an empty table to stay empty.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tomohiro hiramitsu | 2021-03-01 01:56:50 | Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. |
| Previous Message | Dave Cramer | 2021-03-01 01:28:04 | Re: BUG #16893: JDBC Error |