Hi Alvaro,
On Thu, Aug 6, 2020 at 4:25 PM kato-...@fujitsu.com
<kato-...@fujitsu.com> wrote:
> On Wednesday, August 5, 2020 9:43 AM I wrote:
> > I'll report the result before the end of August .
>
> I test v2-0001-build-partdesc-memcxt.patch at 9a9db08ae4 and it is ok.
Is this patch meant for HEAD or back-patching? I ask because v13 got this:
commit 5b9312378e2f8fb35ef4584aea351c3319a10422
Author: Tom Lane <t...@sss.pgh.pa.us>
Date: Wed Dec 25 14:43:13 2019 -0500
Load relcache entries' partitioning data on-demand, not immediately.
which prevents a partitioned table's PartitionDesc from being rebuilt
repeatedly as would happen before this commit in Kato-san's case,
because it moves RelationBuildPartitionDesc out of the relcache flush
code path.
So, the OOM situation that Kato-san original reported should not occur
as of v13.
--
Amit Langote
EnterpriseDB: http://www.enterprisedb.com
