Re: How can i be certain autovacuum is causing reuse if table still grows

From: Holger Jakobs <holger(at)jakobs(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: How can i be certain autovacuum is causing reuse if table still grows
Date: 2020-07-28 06:44:18
Message-ID: ab846992-fa14-9071-07ca-157cef437c43@jakobs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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:
>>
>> Thank you Ron but this table has no date column.
>>
>> It has one line for each page of each scanned document.
>>
>> ------------------------------------------------------------------------
>> *De:* Ron <ronljohnsonjr(at)gmail(dot)com>
>> *Enviado:* segunda-feira, 27 de julho de 2020 18:27
>> *Para:* pgsql-admin(at)lists(dot)postgresql(dot)org
>> <pgsql-admin(at)lists(dot)postgresql(dot)org>
>> *Assunto:* Re: How can i be certain autovacuum is causing reuse if
>> table still grows
>>  
>> 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.
>>> ------------------------------------------------------------------------
>>> *De:* David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
>>> <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>
>>> *Enviado:* segunda-feira, 27 de julho de 2020 17:17
>>> *Para:* Sidney Aloisio Ferreira Pryor <sidney(at)tjrj(dot)jus(dot)br>
>>> <mailto:sidney(at)tjrj(dot)jus(dot)br>
>>> *Cc:* pgsql-admin(at)lists(dot)postgresql(dot)org
>>> <mailto:pgsql-admin(at)lists(dot)postgresql(dot)org>
>>> <pgsql-admin(at)lists(dot)postgresql(dot)org>
>>> <mailto:pgsql-admin(at)lists(dot)postgresql(dot)org>
>>> *Assunto:* Re: How can i be certain autovacuum is causing reuse if
>>> table still grows
>>>  
>>> On Monday, July 27, 2020, Sidney Aloisio Ferreira Pryor
>>> <sidney(at)tjrj(dot)jus(dot)br <mailto:sidney(at)tjrj(dot)jus(dot)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)
>>> (1 rows)
>>>
>>>
>>> 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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message soumik.bhattacharjee 2020-07-28 08:04:12 Cache Hit Ratio%
Previous Message Ron 2020-07-28 05:15:54 Re: How can i be certain autovacuum is causing reuse if table still grows