Heikki Linnakangas <hlinnakan...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
