From: Bruno Wolff III <bruno@wolff.to>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Should pg 11 use a lot more memory building an spgist index?
Date: Wed, 24 Oct 2018 03:37:48 -0500
Message-ID: <20181024083748.GA3296@wolff.to> (raw)
In-Reply-To: <19003.1540370028@sss.pgh.pa.us>
References: <20181024012314.GA27428@wolff.to>
<19003.1540370028@sss.pgh.pa.us>
On Wed, Oct 24, 2018 at 09:33:48 +0100,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>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?
I'll try. I think I should only need the geolite data to cause the problem
and I can share that publicly. So far the problem seems to be happening
consistently. I'll work on this at the office, but probably won't get it
done until the afternoon.
If I have a substantial database dump file to provide for reproducing this
do you prefer it on a web server somewhere? I expect that mailing very
large attachments to the lists is a bad idea.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: bruno@wolff.to, tgl@sss.pgh.pa.us, pgsql-general@lists.postgresql.org
Subject: Re: Should pg 11 use a lot more memory building an spgist index?
In-Reply-To: <20181024083748.GA3296@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox