Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX

From: Wes <wespvp(at)msg(dot)bt(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX
Date: 2008-01-25 16:14:04
Message-ID: C3BF66EC.6FF1A%wespvp@msg.bt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 1/25/08 5:40 AM, "Gregory Stark" <stark(at)enterprisedb(dot)com> wrote:

> It shouldn't make a big difference. fsync only happens at the end of a
> transaction or at a checkpoint.
>
> Since you're concerned with very long operations the slowdown at the end of
> the transaction won't make a big difference.

Ok, I didn't realize that.

> Checkpoints could be an issue, but you would be better off just raising
> checkpoint_segments and/or checkpoint_timeout to make sure you don't get one
> more often than once every few minutes when you're doing large operations like
> this.

I have checkpoint_segments set to 60, and no warnings showing up in the log.

Wes

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Clark 2008-01-25 16:23:51 Re: best way to query
Previous Message Tom Lane 2008-01-25 15:48:01 Re: best way to query

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-25 16:46:00 Re: Default index tablespace
Previous Message Tom Lane 2008-01-25 15:44:19 Re: Truncate Triggers