On Mon, March 24, 2008 9:40 pm, Christopher Browne wrote:
> Yes, it's busy chugging away reindexing the tables.  That's the main
> thing that finishTableAfterCopy() does.

ding-ding.

> We drop the indexes before loading data in, then reindex, as that is
> *WAY* faster than loading the data into a table with indexes on it.

agreed.

> If the table is really big, it is not remarkable for it to take 7h to
> regenerate indexes, and the approach we took saved you way more than
> 7h worth of subscription time...

ok - looks like it's about _reindexing_ and not the subsequent ANALYZE.

Thanks to all for the enlightening comments.

Regards
Henry