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

help / color / mirror / Atom feed
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
To: Amit Langote <amitlangote09@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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 15:10:04 +0900
Message-ID: <fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1> (raw)
In-Reply-To: <CA+HiwqERg6X3xjSmOmNGdMB5Hrx9eQTUDxOG_+PZ4xYuDLw5Kg@mail.gmail.com>
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>

On 2021/03/11 9:39, Amit Langote wrote:
> On Thu, Mar 11, 2021 at 4:25 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Amit Langote <amitlangote09@gmail.com> writes:
>>> On Wed, Mar 10, 2021 at 8:37 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> Hmm.  So, the key point is that the values coming from the partitioned
>>>> child table are injected into the test query as parameters, not as
>>>> column references, thus it doesn't matter *to the test query* what
>>>> numbers the referencing columns have in that child.  We just have to
>>>> be sure we pass the right parameter values.
>>
>>> Right.
>>
>> I did some cosmetic fooling with this (mostly, rewriting the comments
>> YA time) and pushed it.
> 
> Perfect.   Thanks for your time on this.


Thanks for fixing the problem! :-D


Regards,
Tatsuro Yamada






view thread (53+ messages)  latest in thread

Message-ID: <fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1>
Permalink:  ../fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1/
Also on:    postgresql.org/message-id/fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1

 · 

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: tatsuro.yamada.tf@nttcom.co.jp, amitlangote09@gmail.com, tgl@sss.pgh.pa.us, 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: <fc451a2f-93db-2c19-d7d3-11c7bfc4950a@nttcom.co.jp_1>

* 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