| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | killerwzb(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19642: Include column name in error message when varchar(n) length limit is exceeded |
| Date: | 2026-08-28 13:16:14 |
| Message-ID: | CAKFQuwYHsUtLQpTKTj65bMpRAtt4Gt22jswDLN0V2LaXNb5LCA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Aug 28, 2026 at 8:57 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19642
> Logged by: zhibin wang
> Email address: killerwzb(at)gmail(dot)com
> PostgreSQL version: 18.4
> Operating system: centos7
> Description:
>
> Dear PostgreSQL Developers,
> I am writing to suggest an improvement to the error reporting mechanism for
> data type length constraints.
> Currently, when an insertion fails due to exceeding the varchar(n) limit,
> the error message only states that the value is too long for the type, but
> it does not specify which column caused the failure.
>
>
This is not a bug; and it is a frequent feature request you should be able
to find prior discussions for in the mailing list archives.
If you think you can contribute to moving efforts forward on getting
something like this implemented you should peruse the archives to figure
out why it hasn't been accomplished yet. Otherwise, just know that your
voice has been heard and it may or may not be something that gets
implemented in the future.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2026-08-28 13:28:02 | Re: BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description |
| Previous Message | PG Bug reporting form | 2026-08-28 12:42:44 | BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description |