| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: [DOCS] Let's document a bytea bug |
| Date: | 2020-08-03 22:04:47 |
| Message-ID: | 20200803220447.GG17519@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Aug 3, 2020 at 05:39:47PM -0400, Alvaro Herrera wrote:
> On 2020-Aug-03, Bruce Momjian wrote:
>
> > So, the character and octet length is 600 million, but on output, that
> > will be expanded, and both SELECT and pg_dump fail. I also can't see
> > how to improve the error message since it happens so low in the stack.
>
> I think you'll find commits fa2fa9955280 and b66adb7b0c83 amusing.
Yeah, I saw those, but they were dealing with tuple length limits, but I
also saw they were reverted, so this is a hard problem.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-08-03 22:24:21 | Re: "innovative Serializable Snapshot Isolation (SSI) level" |
| Previous Message | Alvaro Herrera | 2020-08-03 21:39:47 | Re: [DOCS] Let's document a bytea bug |