| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simplify newNode() |
| Date: | 2023-12-14 22:56:25 |
| Message-ID: | CA+hUKGJwr51DGYfQsmHi-njS08O+wiU__nYEnYu+kVcnM8E2Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 15, 2023 at 11:44 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> > Yeah, +1 on removing all that, including MemoryContextAllocZeroAligned.
> > It's not doing any good as it is, as it gets compiled to be identical to
> > MemoryContextAllocZero.
>
> Also not so here. Admittedly, my results don't make much of a case
> for keeping the two code paths, even on compilers where it matters.
FWIW here is what I figured out once about why it gets compiled the
same these days:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2023-12-14 23:52:54 | Re: Memory consumed by paths during partitionwise join planning |
| Previous Message | Tom Lane | 2023-12-14 22:44:14 | Re: Simplify newNode() |