Re: IndexJoin memory problem using spgist and boxes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: IndexJoin memory problem using spgist and boxes
Date
Msg-id 26107.1520192782@sss.pgh.pa.us
Whole thread Raw
In response to Re: IndexJoin memory problem using spgist and boxes  (Anton Dignös <dignoes@inf.unibz.it>)
List pgsql-hackers
=?UTF-8?Q?Anton_Dign=C3=B6s?= <dignoes@inf.unibz.it> writes:
>> 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.

> The problem before this patch was that the traversalMemoryContext in
> this function was set to per-query lifetime.
> The memory allocations in the per-query lifetime caused this high
> memory consumption.

Yeah ...

> I changed the temporary context to per-index-scan so that it can also
> be used for traversalMemoryContext.

But we have also had many complaints about leakage across a single index
scan, if it traverses many index entries.  I think you're just moving the
pain out of one use-case and into another.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] user-defined numeric data types triggering ERROR: unsupported type
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] user-defined numeric data types triggering ERROR:unsupported type