pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: pgsql-general@lists.postgresql.org
Subject: Re: Should pg 11 use a lot more memory building an spgist index?
Date: Thu, 25 Oct 2018 07:10:29 -0500
Message-ID: <20181025121029.GA25010@wolff.to> (raw)
In-Reply-To: <20181025024144.GA17798@wolff.to>
References: <20181024012314.GA27428@wolff.to>
	<20181025024144.GA17798@wolff.to>

It looks like it got past creating the exclude constraint based on the 
ordering of commands in the dump file. However creating a more normal 
spgist index is taking a very long time with a lot of disk wait time. 
CPU usage seems pretty low for the amount of time it has been working 
on building that index, but maybe that is normal for building indexes.
I used the almost the default postgresql.conf on my workstation. I bumped 
up the limits in a few places on the server that could have allowed a lot 
more memory to be used especially if the index creation was parallelized. 
While the load is running I'll see if I can tell if there is a memory leak 
with this index build. Once it finishes, I can dump a specific table 
and test building the exclude spgist index with some different settings 
to see if I can reproduce the out of memory error with a lot less data 
then is in the whole database.




view thread (24+ messages)  latest in thread

Message-ID: <20181025121029.GA25010@wolff.to>
Permalink:  ../20181025121029.GA25010@wolff.to/
Also on:    postgresql.org/message-id/20181025121029.GA25010@wolff.to

 · 

reply

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, pgsql-general@lists.postgresql.org
  Subject: Re: Should pg 11 use a lot more memory building an spgist index?
  In-Reply-To: <20181025121029.GA25010@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