Date: Mon, 3 Aug 2020 18:04:47 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: "Andrey M. Borodin" <x4mmm@yandex-team.ru>,
	Anna Akenteva <a.akenteva@postgrespro.ru>,
	pgsql-docs@postgresql.org
Subject: Re: [DOCS] Let's document a bytea bug
Message-ID: <20200803220447.GG17519@momjian.us>
References: <20200803202042.GC17519@momjian.us>
 <20200803213947.GA1118@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200803213947.GA1118@alvherre.pgsql>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee