| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory leak in gingetbitmap |
| Date: | 2015-01-29 16:29:17 |
| Message-ID: | 7196.1422548957@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-01-29 16:34:08 | Re: Parallel Seq Scan |
| Previous Message | Tom Lane | 2015-01-29 16:10:09 | Re: pg_dump with both --serializable-deferrable and -j |