So you can use your SERIAL (or GENERATED AS IDENTITY) column for this. If you don't have this, you might add a DATE DEFAULT CURRENT_DATE column, even if it's of no use except being the partition key.
Am 28.07.20 um 05:32 schrieb Ron:
Any key that "increases linearly over time" is a chronological key; sequences are a perfect example.
On 7/27/20 4:38 PM, Sidney Aloisio Ferreira Pryor wrote:
P {margin-top:0;margin-bottom:0;} Thank you Ron but this table has no date column.
It has one line for each page of each scanned document.
Another suggestion is to partition the table by a chronological key, so that only a fraction of the table needs to be vacuumed.
On 7/27/20 3:36 PM, Sidney Aloisio Ferreira Pryor wrote:
Thank you, David.
So can i assume that autovacuum only release dead tuples when it ends its execution?
Autovacuum is not finishing and is running for days.
We did not find a parameter to limit autovacuum executing time.
Do you have any recomendation?
Thank you.
Sidney.
On Monday, July 27, 2020, Sidney Aloisio Ferreira Pryor <
sidney@tjrj.jus.br> wrote:
Hi, we have a 9.6.5 postgres
Autovacuum is set with default parameters and is running on this table for days without naping or stopping.
3285 | -5 days -23:33:10.792166 | postgres | autovacuum: VACUUM ANALYZE public.flip_pagina_edicao (to prevent wraparound)
Its probably best avoid drawing conclusions here until the anti-wraparound vacuum has completed and you’ve updated to the latest minor version of PostgreSQL.
David J.
--
Angular momentum makes the world go 'round.
--
Angular momentum makes the world go 'round.
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012