Re: pgsql: Generational memory allocator - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Generational memory allocator
Date
Msg-id CANP8+jKoT=Pg5W_3FcKiDf+FMrJhFYacxt_g5E0=tkmb5s8M6g@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Generational memory allocator  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: Generational memory allocator  (Tomas Vondra <tv@fuzzy.cz>)
Re: pgsql: Generational memory allocator  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
On 23 November 2017 at 11:16, Andres Freund <andres@anarazel.de> wrote:
> Hi,
>
> On 2017-11-22 18:48:19 +0000, Simon Riggs wrote:
>> Generational memory allocator
>>
>> Add new style of memory allocator, known as Generational
>> appropriate for use in cases where memory is allocated
>> and then freed in roughly oldest first order (FIFO).
>>
>> Use new allocator for logical decoding’s reorderbuffer
>> to significantly reduce memory usage and improve performance.
>
> Looks like it's not quite valgrind clean:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2017-11-22%2022%3A30%3A01

It doesn't report anything useful that would allow me to fix this.

Please enable some info reporting on the animal.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: doc: mention wal_receiver_status_interval as GUC affectinglogic
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Convert documentation to DocBook XML