| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Steve Poe" <spoe(at)sfnet(dot)cc> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Help tuning postgres |
| Date: | 2005-10-12 18:17:47 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD59C@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>
> Would it not be faster to do a dump/reload of the table than reindex
or
> is it about the same?
>
reindex is probably faster, but that's not the point. you can reindex a
running system whereas dump/restore requires downtime unless you work
everything into a transaction, which is headache, and dangerous.
reindex locking is very granular, in that it only acquires a excl. lock
on one index at a time and while doing so reading is possible (writes
will wait).
in 8.1 we get a fire and forget reindex database xyz which is about as
good as it gets without a dump/load or full vacuum.
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Nickel | 2005-10-12 20:40:24 | Sequential scan on FK join |
| Previous Message | Steve Poe | 2005-10-12 17:32:05 | Re: Help tuning postgres |