From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Japin Li <japinli(at)hotmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Inconsistent error message for varchar(n) |
Date: | 2022-08-31 23:45:34 |
Message-ID: | Yw/ynsGKuCAi9+mW@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
8On Tue, Aug 16, 2022 at 09:56:17PM -0400, Bruce Momjian wrote:
> On Sun, Nov 14, 2021 at 10:33:19AM +0800, Japin Li wrote:
> > Oh! I didn't consider this situation. Since the max size of varchar cannot
> > exceed 10485760, however, I cannot find this in documentation [1]. Is there
> > something I missed? Should we mention this in the documentation?
> >
> > [1] https://www.postgresql.org/docs/devel/datatype-character.html
>
> Sorry for my long delay in reviewing this issue. You are correct this
> should be documented --- patch attached.
Patch applied back to PG 10. Thanks for the report.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2022-09-01 00:05:36 | Re: pg15b3: recovery fails with wal prefetch enabled |
Previous Message | Bruce Momjian | 2022-08-31 23:29:12 | Re: Doc patch |