Re: A potential memory leak on Merge Join when Sort node is not below Materialize node

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, Önder Kalacı <onderkalaci(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: A potential memory leak on Merge Join when Sort node is not below Materialize node
Date: 2022-09-28 23:57:52
Message-ID: YzTfgCjvd7+PGbGi@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 28, 2022 at 07:35:07PM -0400, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> Wouldn't it be better to have 3a58176 reflect the non-optimization
>> path in the EXPLAIN output of a new regression test if none of the
>> existing tests are able to show any difference?
>
> This decision is not visible in EXPLAIN in any case.

Okay, thanks!
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhang Mingli 2022-09-29 01:05:18 Re: Refactor UnpinBuffer()
Previous Message Tom Lane 2022-09-28 23:35:07 Re: A potential memory leak on Merge Join when Sort node is not below Materialize node