On Thursday November 11 2004 6:26, Ed L. wrote:
>
> So I hacked cleanup_thread.c to skip the if-statement that does the
> vacuum with query3.  Now I'm seeing it do its 2nd round of
> truncateTable()-copy during the copy set operation under the same backend
> pid.  I can't recreate this behavior using the same code on a small
> pgbench database.
>
> Is there any normal circumstance under which copy set would do it more
> than once??

I was running with a copy set patch, so I've removed that and am trying 
again.  Autovacuum is running on the master doing ANALYZE on these tables, 
but I disabled any VACUUMing during the copy set.  

Would analyze have any detrimental effect to slon copy set logic?

Ed