Re: Commitfest 2023-03 starting tomorrow!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: 2023-04-21 17:41:08
Message-ID: 3366805.1682098868@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Apr 21, 2023 at 12:49 PM Melanie Plageman
> <melanieplageman(at)gmail(dot)com> wrote:
>> If using a separate memory context solely for the purpose of accounting
>> is considered an anti-pattern, ...

> This thread isn't the right place to argue about the merits of that
> patch, at least IMHO, but I don't think that's an anti-pattern.

I didn't say that either. If the proposal is to apply only that change,
I could be on board with doing that post-feature-freeze. I just don't
think the parts of the patch that change the memory management heuristics
are ready.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-04-21 17:46:25 Re: Order changes in PG16 since ICU introduction
Previous Message Gurjeet Singh 2023-04-21 17:39:45 Re: Correct the documentation for work_mem