Hello all,

During an initial replication from a master to many slaves, why does slony
perform an ANALYZE after the COPY?  For paltry tables this is OK, but for
massive (multiple GB) tables, this is something which takes frigging
*days* per table.

Besides, what's the point of analyzing after a fresh COPY?

Even if there is a valid reason to analyze after a copy, is there a way to
disable this behavior (short of hacking the src)?  The docs don't tell me
much.

Thanks
Henry