| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Should pg 11 use a lot more memory building an spgist index? |
| Date: | 2018-10-24 08:37:48 |
| Message-ID: | 20181024083748.GA3296@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Oct 24, 2018 at 09:33:48 +0100,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Bruno Wolff III <bruno(at)wolff(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-24 09:21:11 | Re: Should pg 11 use a lot more memory building an spgist index? |
| Previous Message | Tom Lane | 2018-10-24 08:33:48 | Re: Should pg 11 use a lot more memory building an spgist index? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-24 09:21:11 | Re: Should pg 11 use a lot more memory building an spgist index? |
| Previous Message | Dilip Kumar | 2018-10-24 08:34:47 | Re: Side effect of CVE-2017-7484 fix? |