| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| 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-24 05:06:42 |
| Message-ID: | e86ea41fd721105ded8b5cd02601ead43750afe0.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2019-09-24 07:29:54 | Re: How to represent a bi-directional list in db? |
| Previous Message | Andrew Gierth | 2019-09-24 02:40:12 | Re: How to get timezone offset in timestamp with time zone AT TIME ZONE output. |