| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Wes" <wespvp(at)msg(dot)bt(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 11:40:24 |
| Message-ID: | 873asmjfpz.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Wes" <wespvp(at)msg(dot)bt(dot)com> writes:
> I guess I should also turn off fsync for the duration.
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.
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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Clark | 2008-01-25 13:03:57 | best way to query |
| Previous Message | Gregory Stark | 2008-01-25 11:35:24 | Re: check constraint question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-01-25 12:01:11 | Default index tablespace |
| Previous Message | Simon Riggs | 2008-01-25 11:40:19 | Truncate Triggers |