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

From Simon Riggs
Subject Re: pgsql: Generational memory allocator
Date
Msg-id CANP8+jJTz1RmjmnE2biK71yAEJxgcHT=pXjMX63FfvMLU3Wx7Q@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Generational memory allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 25 November 2017 at 12:25, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
>> For me, this patch fixes the valgrind failures inside generation.c
>> itself, but I still see one more in the test_decoding run: ...
>> Not sure what to make of this: the stack traces make it look unrelated
>> to the GenerationContext changes, but if it's not related, how come
>> skink was passing before that patch went in?
>
> I've pushed fixes for everything that I could find wrong in generation.c
> (and there was a lot :-().

Thanks very much for doing that.  I'll review changes and comment.

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


pgsql-committers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pgsql: Generational memory allocator
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Generational memory allocator