Horton
Menu

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

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-general@lists.postgresql.org
Date: 2018-10-24T08:33:48Z
Lists: pgsql-hackers 
Bruno Wolff III <bruno@wolff.to> writes:
> While reloading a database cluster to move from 10.5 to 11, I'm getting 
> out of memory crashes that I did see when doing reloads on pg 10.
> The statement flagged in the log is this:
> 2018-10-23 16:44:34.815 CDT [126839] STATEMENT:  ALTER TABLE ONLY public.iplocation
> 	    ADD CONSTRAINT overlap EXCLUDE USING spgist (network WITH &&);

Hm, there's a fair amount of new code in SP-GIST in v11, so maybe you've
hit a memory leak in that.  Can you create a self-contained test case?

			regards, tom lane

Commits

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

  1. Fix memory leak in repeated SPGIST index scans.

  2. Add support for nearest-neighbor (KNN) searches to SP-GiST