From: Steven Flatt <steven.flatt@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Vivek Khera <vivek@khera.org>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: When/if to Reindex
Date: Thu, 9 Aug 2007 09:51:42 -0400
Message-ID: <357fa7590708090651p71b9bc47n66739f8dbbb4ff57@mail.gmail.com> (raw)
In-Reply-To: <11801.1186624308@sss.pgh.pa.us>
References: <357fa7590707181008k65ab2f20l55bebb3c14f52770@mail.gmail.com>
<38118C09-FC0A-4CCB-9461-FC6D29D81EE4@khera.org>
<357fa7590708081212p7b19cbbbn39dbadae8603edd6@mail.gmail.com>
<20070808152757.9eb9bbcc.wmoran@collaborativefusion.com>
<11801.1186624308@sss.pgh.pa.us>
On 8/8/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I'd make the same remark about Steven's case: if possible, don't create
> the indexes at all until you've loaded the table fully.
We considered this, however in some of our 12-hour partitions, there are
upwards of 50 or 60 million rows near the end of the 12 hours so read
performance gets bad on the current partition very quickly if there are no
indexes.
It makes more sense for us to have ~1 hour's worth of reindexing afterwards
during which read performance on that partition is "compromised".
Steve
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: steven.flatt@gmail.com, tgl@sss.pgh.pa.us, wmoran@collaborativefusion.com, vivek@khera.org
Subject: Re: When/if to Reindex
In-Reply-To: <357fa7590708090651p71b9bc47n66739f8dbbb4ff57@mail.gmail.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