pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Yinan Li <yinanli@cse.ust.hk>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: how to improve the performance of creating index
Date: Fri, 19 Oct 2007 15:50:07 +0100
Message-ID: <4718C41F.8090202@enterprisedb.com> (raw)
In-Reply-To: <01cb01c8125e$011183d0$03348b70$@ust.hk>
References: <01c601c81247$3b8c5650$b2a502f0$@ust.hk>
	<47189D0F.6090707@enterprisedb.com>
	<01cb01c8125e$011183d0$03348b70$@ust.hk>

Please keep the list cc'd so that others can help.

Yinan Li wrote:
> What version of Postgres are you using?
> 8.2.4
> How much RAM does the box have?
> 2G
> How big is the table? 
> 256M tuples, each tuple contains 2 integers.
> How long does the index build take?
> About 2 hours
> What kind of an I/O system do you have?
> A SATA disk (7200 rpm)

2 hours does sound like a very long time. With a table like that, we're
talking about ~7-9 GB worth of data if I did the math right.

You could try lowering shared_buffers to something like 50 MB while you
build the index, to leave more RAM available for OS caching.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com



view thread (5+ messages)  latest in thread

Message-ID: <4718C41F.8090202@enterprisedb.com>
Permalink:  ../4718C41F.8090202@enterprisedb.com/
Also on:    postgresql.org/message-id/4718C41F.8090202@enterprisedb.com

 · 

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-performance@postgresql.org
  Cc: heikki@enterprisedb.com, yinanli@cse.ust.hk
  Subject: Re: how to improve the performance of creating index
  In-Reply-To: <4718C41F.8090202@enterprisedb.com>

* 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