| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | "kato-sho(at)fujitsu(dot)com" <kato-sho(at)fujitsu(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Creating foreign key on partitioned table is too slow |
| Date: | 2020-08-19 05:02:55 |
| Message-ID: | CA+HiwqF8+F-qDc9gcJ2dPWG7O8xU5b5nqJQ0CQkSXnRZy0CHmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Alvaro,
On Thu, Aug 6, 2020 at 4:25 PM kato-sho(at)fujitsu(dot)com
<kato-sho(at)fujitsu(dot)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 <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiro Ikeda | 2020-08-19 05:10:08 | RE: New statistics for tuning WAL buffer size |
| Previous Message | tsunakawa.takay@fujitsu.com | 2020-08-19 04:49:02 | RE: New statistics for tuning WAL buffer size |