pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: keisuke kuroda <keisuke.kuroda.3862@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: tatsuhito.kasahara.rd@hco.ntt.co.jp
Subject: Re: Huge memory consumption on partitioned table with FKs
Date: Thu, 11 Mar 2021 12:01:56 -0500
Message-ID: <2305128.1615482116@sss.pgh.pa.us> (raw)
In-Reply-To: <fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1>
References: <20201203.142857.1823750032495295791.horikyota.ntt@gmail.com>
	<CA+HiwqEOrfN9b=f3sDmySPGc4gO-L_VMFHXLLxVmmdP34e64+w@mail.gmail.com>
	<CANDwggJcdu3Cbtr50X+zLXoh+rB-MYfp=GGqbfv8TVS3VT4tuA@mail.gmail.com>
	<20201204.144822.1258776940142794322.horikyota.ntt@gmail.com>
	<CA+HiwqGrr2YOO6voBM6m_OAc9w-WMxe1gOuQ-UyDPin6zJtyZw@mail.gmail.com>
	<1412267.1614891636@sss.pgh.pa.us>
	<CA+HiwqFbYQ+6xKyDJmb18+vHA1+KuF8VMXEtVO-Y68tTJow5CQ@mail.gmail.com>
	<2050317.1615333064@sss.pgh.pa.us>
	<CA+HiwqE7xvHBN3dm3ee2XU++tjuxHv5giyrmaE7McSeG6yPdoA@mail.gmail.com>
	<2187988.1615404297@sss.pgh.pa.us>
	<CA+HiwqERg6X3xjSmOmNGdMB5Hrx9eQTUDxOG_+PZ4xYuDLw5Kg@mail.gmail.com>
	<fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1>

Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp> writes:
> Thanks for fixing the problem! :-D

Hmm, I'm not sure we're done with this patch:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=husky&dt=2021-03-10%2021%3A09%3A32

The critical log extract is

2021-03-11 05:10:13.012 CET [21574:1082] pg_regress/foreign_key LOG:  statement: insert into fk_notpartitioned_pk (a, b)
	  select 2048, x from generate_series(1,10) x;
2021-03-11 05:10:13.104 CET [11830:368] LOG:  server process (PID 21574) was terminated by signal 11: Segmentation fault
2021-03-11 05:10:13.104 CET [11830:369] DETAIL:  Failed process was running: insert into fk_notpartitioned_pk (a, b)
	  select 2048, x from generate_series(1,10) x;

Now, maybe it's a coincidence that husky failed on a
partitioned-foreign-key test right after this patch went in, but I bet
not.  Since husky runs CLOBBER_CACHE_ALWAYS, it looks to me like we've
overlooked some cache-reset scenario or other.

			regards, tom lane





view thread (53+ messages)  latest in thread

Message-ID: <2305128.1615482116@sss.pgh.pa.us>
Permalink:  ../2305128.1615482116@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2305128.1615482116@sss.pgh.pa.us

 · 

reply
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: tgl@sss.pgh.pa.us, tatsuro.yamada.tf@nttcom.co.jp, amitlangote09@gmail.com, horikyota.ntt@gmail.com, keisuke.kuroda.3862@gmail.com, alvherre@alvh.no-ip.org, pgsql-hackers@lists.postgresql.org, tatsuhito.kasahara.rd@hco.ntt.co.jp
  Subject: Re: Huge memory consumption on partitioned table with FKs
  In-Reply-To: <2305128.1615482116@sss.pgh.pa.us>

* 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