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 05:13:06
Message-ID: CAH2-Wz=jrnCVydbwSHwnE3DZ_gALxHpf9kJ-QjfBsZQz+p-VaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 28, 2022 at 9:59 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> select b from t1 order by b offset 1000000;
>
> Master:
> latency average = 344.763 ms
>
> Patched:
> latency average = 268.374 ms
>
> about 28% faster.

That's more like it!

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-09-29 05:27:53 Re: more descriptive message for process termination due to max_slot_wal_keep_size
Previous Message David Rowley 2022-09-29 05:12:06 Have nodeSort.c use datum sorts single-value byref types