Here's what I found when the thing was finally completed:
Hardware:
Dual AMD 1600+, 4GB Ram, 110GB RAID, 2GB in shared memory for Pg
Environment:
We turned off most access to the database, load was down to about .2
when we started. We *did not* run a single process, as the manuals
recommended.
Reindex took ~45 Minutes on a single table with 10 indices, and
1.2Million Tuples. The reindex process ran on only a single CPU.
- Ericson Smith
Web Developer
http://www.did-it.com
eric@did-it.com
On Wed, 2002-07-31 at 12:32, Naomi Walker wrote:
> At 05:58 AM 7/31/2002 , Ericson Smith wrote:
> >A quick question.
> >
> >We're reindexing a table with 1.2 million tuples and around 10 indexes.
> >
> ># REINDEX TABLE tlogs;
> >
> >Does anyone have any anecdotes about the time that a reindex should
> >take?
>
> I would imagine it depends on how much you have in the way of system
> resources (memory, cpu (how fast, how many)) at the time it is done.
>
> But to the list, supposing the entire machine was idle, would a reindex
> spread itself amount cpu's, and perform the task in pieces, or is it bound
> to a cpu?
>
>
>
> >- Ericson Smith
> >http://www.did-it.com
> >eric@did-it.com
> >
> >
> >
> >
> >
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 5: Have you checked our extensive FAQ?
> >
> >http://www.postgresql.org/users-lounge/docs/faq.html
>
> ----------------------------------------------------------------------------
> ----------------------------------
> Naomi Walker
> Eldorado Computing, Inc
> Chief Information Officer
> nwalker@eldocomp.com
> 602-604-3100 x242
>
>