Re: BUG #14179: Not enough info in error message

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: dmigowski(at)ikoffice(dot)de
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14179: Not enough info in error message
Date: 2016-06-07 12:36:39
Message-ID: CAKFQuwazFx74MGhPPtMjoJoPeBa0w6tdZMEQ3FSP3Ze_-bMhnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 7, 2016 at 3:50 AM, <dmigowski(at)ikoffice(dot)de> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14179
> Logged by: Daniel Migowski
> Email address: dmigowski(at)ikoffice(dot)de
> PostgreSQL version: 9.5.2
> Operating system: all
> Description:
>
> Hello,
>
> I often get some error like: value too long for type character
> varying(160).
> Not it is hard for me to check which column contained the constraint.
>
>
​This is a frequent complaint with no easy, and in some queries no
possible, solution.​

> I would love to see something like: "value too long for type character
> varying(160) in column mytable.mycolumn"​
>

​CREATE TABLE sample (col text CHECK (length(col) <= 160));​

This would have safed me at least 20 hours during the last years!
>
> If you fix this, please backport to 9.5, and I would immediately upgrade
> all
> our servers.

​Even if this was improved upon it would never be back-ported. It is not a
bug.

​There is more in-depth discussion out there on these lists but I do not
have the time at the moment to search around for it.​

I did check the FAQ and this topic does not appear there :( Maybe it will
in the future...

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Emiel Hermsen 2016-06-07 12:58:54 Case in Order By Ignored without warning or error
Previous Message David G. Johnston 2016-06-07 12:25:01 Re: [BUGS] BUG #14155: bloom index error with unlogged table