| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Generational memory allocator |
| Date: | 2017-11-23 09:57:10 |
| Message-ID: | CANP8+jKoT=Pg5W_3FcKiDf+FMrJhFYacxt_g5E0=tkmb5s8M6g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 23 November 2017 at 11:16, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-11-23 14:51:23 | pgsql: Convert documentation to DocBook XML |
| Previous Message | Fujii Masao | 2017-11-23 07:49:16 | pgsql: doc: mention wal_receiver_status_interval as GUC affecting logic |