| From: | Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Anton Dignös <dignoes(at)inf(dot)unibz(dot)it>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: IndexJoin memory problem using spgist and boxes |
| Date: | 2018-03-02 18:47:27 |
| Message-ID: | 658ef60b-2773-d649-2313-61ee69800062@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Anton,
I can reproduce the high memory consumption with your queries.
Looking at the patch, I see that you changed the lifetime of the
temporary context from per-tuple to per-index-scan. It is not obvious
that this change is correct. Could you explain, what memory context are
involved in the scan, and what their lifetimes are, before and after
your changes? What are these memory allocations that are causing the
high consumption, and what code makes them? This will make it easier to
understand your changes.
Also, this link doesn't open for me.
--
Alexander Kuzmenkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robbie Harwood | 2018-03-02 19:19:17 | Re: Kerberos test suite |
| Previous Message | Robert Haas | 2018-03-02 18:42:35 | Re: [HACKERS] Partition-wise aggregation/grouping |