Re: Autovacuum lock conflict

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Christophe Escobar <christophe(dot)esco(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Autovacuum lock conflict
Date: 2019-09-23 19:53:58
Message-ID: CAHOFxGr_L9r2j41TCc9vPtZ4YQ8n2C-udthnCJDS2qRMHivG5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> - 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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Corey Taylor 2019-09-23 20:58:22 Re: postgres 9.6: insert into select finishes only in pgadmin not psql
Previous Message Adrian Klaver 2019-09-23 19:37:23 Re: can't install pg 12 beta on centos 6