Re: Should pg 11 use a lot more memory building an spgist index?

Bruno Wolff III <bruno@wolff.to>

From: Bruno Wolff III <bruno@wolff.to>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Amit Langote <amitlangote09@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, akorotkov@postgresql.org, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2018-11-02T21:01:34Z

Lists: pgsql-hackers

I see that a fix got committed. Thanks!
I'll double check it after the point release comes out (which looks like it 
will be next week) and let you know if there is still a problem.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix memory leak in repeated SPGIST index scans.
- 696b0c5fd0a8 12.0 landed
- 95015b1f8e8e 9.4.20 landed
- 92e371f9b143 10.6 landed
- 82dd1c271492 9.3.25 landed
- 558571afc7c4 9.6.11 landed
- 156a737a6b73 9.5.15 landed
- 2493e2c2d167 11.1 landed
Add support for nearest-neighbor (KNN) searches to SP-GiST
- 2a6368343ff4 12.0 cited