From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Scalia <jayknowsunix@gmail.com>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Very long index build time
In-reply-to: 
 <CABzCKRCd=Wx2gHMFZSjBpPQGi4LgFQnGPrw6h+ZpZgV6TcUJFw@mail.gmail.com>
References: 
 <CABzCKRCd=Wx2gHMFZSjBpPQGi4LgFQnGPrw6h+ZpZgV6TcUJFw@mail.gmail.com>
Comments: In-reply-to John Scalia <jayknowsunix@gmail.com>
	message dated "Thu, 09 Feb 2017 08:07:51 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18941.1486662403.1@sss.pgh.pa.us>
Date: Thu, 09 Feb 2017 12:46:43 -0500
Message-ID: <18942.1486662403@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

John Scalia <jayknowsunix@gmail.com> writes:
> I'm building a test database for our data warehouse,and I'm trying to build
> a trigram index on one of the tables with a 4000 character varchar field,
> Yes, I want to change this table at some point to make that attribute a
> text field, along with some other structural changes. but that's in the
> future. This particular table reports to be approximately 420 Gb. My
> question is fairly simple, this index has been building since Tuesday
> morning @ 9:52AM EST - nearly 48 hours. Does this sound like a normal build
> time? The command I used is:

>  CREATE INDEX CONCURRENTLY test_schema_notes_trigram_idx on
> test_schema.notes USING gin (notes gin_trgm_ops);

Well, the first question is whether the index building session is actually
doing anything or just waiting.  Is it consuming CPU time?  It might just
be waiting around for some other transaction to finish --- there are
multiple places in a CREATE INDEX CONCURRENTLY sequence where we have to
wait out all other open transactions.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin