Re: Memory leak in gingetbitmap - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leak in gingetbitmap
Date
Msg-id 7196.1422548957@sss.pgh.pa.us
Whole thread Raw
In response to Memory leak in gingetbitmap  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> [ assorted GIN leaks ]

> I think we need a more whole-sale approach. I'm thinking of adding a new 
> memory context to contain everything related to the scan keys, which can 
> then be destroyed in whole.

> We haven't heard any complaints about this from users, but I think this 
> deserves to be fixed. Perhaps not worth back-patching however.

+1 to using a context instead of a lot of retail pfrees, and I concur
that we shouldn't back-patch (barring seeing some field complaints).
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump with both --serializable-deferrable and -j
Next
From: Jeff Janes
Date:
Subject: Re: Parallel Seq Scan