Re: How to retain lesser paths at add_path()?

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Kohei KaiGai <kaigai(at)heterodb(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Richard Guo <riguo(at)pivotal(dot)io>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How to retain lesser paths at add_path()?
Date: 2021-10-05 17:24:47
Message-ID: 20211005172447.GC28628@ahch-to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sat, Mar 06, 2021 at 06:50:13PM +0900, Kohei KaiGai wrote:
> On the other hand, I'm uncertain whether the pfree(new_path) at the tail
> of add_path makes sense on the modern hardware, because they allow to
> recycle just small amount of memory, then entire memory consumption
> by the optimizer shall be released by MemoryContext mechanism.
> If add_path does not release path-node, the above portion is much simpler.

Hi Kaigai-san,

Do you have an updated patch? Please feel free to resubmit to next CF.
Current CF entry has been marked as RwF.

Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2021-10-05 17:24:58 Re: Polyphase merge is obsolete
Previous Message Peter Geoghegan 2021-10-05 17:22:53 Re: BUG #17212: pg_amcheck fails on checking temporary relations