Postgres Pro
Downloads
Home   >   mailing lists

Re: Reducing System Allocator Thrashing of ExecutorState to Alleviate FDW-related Performance Degradations - Mailing list pgsql-hackers

From David Rowley
Subject Re: Reducing System Allocator Thrashing of ExecutorState to Alleviate FDW-related Performance Degradations
Date
Msg-id CAApHDvqWa7zTHq2mnrfnPqZNiPJj+8e+eBFniuVfk-bmupPo0g@mail.gmail.com
Whole thread Raw
In response to Re: Reducing System Allocator Thrashing of ExecutorState to Alleviate FDW-related Performance Degradations  (Andres Freund <andres@anarazel.de>)
Responses Re: Reducing System Allocator Thrashing of ExecutorState to Alleviate FDW-related Performance Degradations
List pgsql-hackers
Tree view 
On Tue, 21 Feb 2023 at 07:30, Andres Freund <andres@anarazel.de> wrote:
> 2) We should introduce an API mcxt.c API to perform allocations that the
>    caller promises not to individually free.

It's not just pfree. Offhand, there's also repalloc,
GetMemoryChunkSpace and GetMemoryChunkContext too.

I am interested in a bump allocator for tuplesort.c. There it would be
used in isolation and all the code which would touch pointers
allocated by the bump allocator would be self-contained to the
tuplesorting code.

What use case do you have in mind?

David

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Killing off removed rels properly
Next
From: Jeff Davis
Date:
Subject: Re: pg_walinspect memory leaks