Re: pgsql: Generational memory allocator

Hi, On 11/25/2017 02:25 AM, Tom Lane 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

Re: pgsql: Generational memory allocator

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

Re: pgsql: Generational memory allocator

On 24 November 2017 at 09:04, Tom Lane wrote: > Andres Freund writes: >> On 2017-11-23 22:34:57 +0100, Tomas Vondra wrote: >>> Hmmm, I see. Presumably adding this to GenerationChunk (similarly to what we >>> do in AllocChunkData) would address the issue:

pgsql: RLS comment fixes.

RLS comment fixes. The comments in get_policies_for_relation() say that CREATE POLICY does not support defining restrictive policies. This is no longer true, starting from PG10. Branch -- master Details ---

pgsql: RLS comment fixes.

RLS comment fixes. The comments in get_policies_for_relation() say that CREATE POLICY does not support defining restrictive policies. This is no longer true, starting from PG10. Branch -- REL_10_STABLE Details ---