From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: allocation limit for encoding conversion
Date: Thu, 3 Oct 2019 19:04:30 -0300
Message-ID: <20191003220430.GA22467@alvherre.pgsql> (raw)
In-Reply-To: <26768.1570138705@sss.pgh.pa.us>
On 2019-Oct-03, Tom Lane wrote:
> I wrote:
> > [ v2-0001-cope-with-large-encoding-conversions.patch ]
> > [ v2-0002-actually-recover-space-in-repalloc.patch ]
>
> I've pushed these patches (after some more review and cosmetic
> adjustments) and marked the CF entry closed. Andres is welcome
> to see if he can improve the situation further.
Many thanks!
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql-hackers@lists.postgresql.org
Subject: Re: allocation limit for encoding conversion
In-Reply-To: <20191003220430.GA22467@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox