Re: allocation limit for encoding conversion - Mailing list pgsql-hackers

From Tom Lane
Subject Re: allocation limit for encoding conversion
Date
Msg-id 26768.1570138705@sss.pgh.pa.us
Whole thread Raw
In response to Re: allocation limit for encoding conversion  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: allocation limit for encoding conversion
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)
Next
From: Alvaro Herrera
Date:
Subject: Re: allocation limit for encoding conversion