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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-29 01:31:42
Message-ID: CAH2-Wzn4MUtwentRZyDONS4QYFOVVC2OysX_TPOO-5ahQeAKRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 28, 2022 at 6:13 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> Master:
> latency average = 313.197 ms
>
> Patched:
> latency average = 304.335 ms
>
> So not a very impressive speedup there (about 3%)

Worth a try, at least. Having a more consistent interface is valuable
in itself too.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xiaoran Wang 2022-09-29 01:37:59 [patch] Adding an assertion to report too long hash table name
Previous Message David Rowley 2022-09-29 01:12:44 Re: A potential memory leak on Merge Join when Sort node is not below Materialize node