| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:12:18 |
| Message-ID: | CA+TgmoakQVcab7XTsUuChKJTjbdda_x=R8qtJGoEwqyVtzKz9w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. If we
need to keep track of how much memory is being used, it sure sounds
like a better idea to use a memory context for that than to invent
some bespoke infrastructure.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-04-21 17:14:13 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Peter Eisentraut | 2023-04-21 17:11:17 | Re: LLVM strip -x fails |