Re: BUG #14054: "create index using gist ..." on large table never completes.

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: tsingle(at)muddypaddock(dot)com
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14054: "create index using gist ..." on large table never completes.
Date: 2016-04-07 02:21:03
Message-ID: CAMkU=1xnnJtCpj5WGka_Omz=FFnWJEYkJjkVgBoOKN7ivZpWjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 30, 2016 at 1:38 AM, <tsingle(at)muddypaddock(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14054
> Logged by: Tim Singletary
> Email address: tsingle(at)muddypaddock(dot)com
> PostgreSQL version: 9.5.1
> Operating system: osx 10.11.4
> Description:
>
> "create index using gist ..." ran for over three days on 100 million row
> table; completes within a couple hours on a 10 million row table.
>
> Had previously tried same experiment with 9.2.3 on a Linux box where the 100
> million row table's index built within 5 hours.
>
> The table looks like
>
> CREATE TABLE mock (
> handle INT NOT NULL
> ,lowest INT NOT NULL
> ,highest INT NOT NULL
> ,stuff TEXT
> );
>
> Data was randomly generated.

"Randomly generated" covers a lot of territory and is not sufficient
to be reproducible. Please provide the random generator.

Thanks,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2016-04-07 02:41:25 Re: BUG #14050: "could not reserve shared memory region" in postgresql log
Previous Message David Rowley 2016-04-07 01:59:29 Re: BUG #14067: Wrong result of <select distinct geometry from XXX>