Re: truncate/create slowness

> It's possible you could get out of this by vacuum full and then reindex
> each catalog, but it might be easier to dump and reload the database ...

I've got a similar issue, but caused by neglect rather than anything to to
with pg_autovacuum.

Do you have any rules of thumb for deciding when a pg_dumpall/restore is
likely to be faster than a vacuum full?  Or perhaps more straightforwardly,
how would you expect the time required for a vacuum full to scale with pages
used and rows in the table?

Thanks

Julian Scarfe