Re: Autovacuum lock conflict

On Mon, 2019-09-23 at 13:53 -0600, Michael Lewis wrote:
> > - For tables that receive only INSERTs, schedule a regular VACUUM
> >   with "cron" or similar.  Unfortunately, PostgreSQL isn't very
> > smart
> >   about vacuuming insert-only tables.
> 
> 
> What is the need to vacuum on an insert only table? Does that just
> maintain the freespace map?

No, the idea is to get rows frozen *before* autovacuum launches
an anti-wraparound vacuum.
You could launch VACUUM (FREEZE) for best effect.

This way you can schedule the operation so that it doesn't
interfere with your other activities.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com