From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: How can i be certain autovacuum is causing reuse if table still grows
Date: Tue, 28 Jul 2020 08:44:18 +0200
Message-ID: <ab846992-fa14-9071-07ca-157cef437c43@jakobs.com> (raw)
In-Reply-To: <c730174f-9ec9-561a-d3ae-f736cd366c64@gmail.com>
References: <FR1PR80MB071069E71B2758BB9D187EC18C770@FR1PR80MB0710.lamprd80.prod.outlook.com>
<CP2PR80MB0707AE54D878CA370750BE908C720@CP2PR80MB0707.lamprd80.prod.outlook.com>
<CAKFQuwYRfH0JMfubcKL=U6oo1cXrtb44H5O+ywXyuKDKg96_KA@mail.gmail.com>
<CP2PR80MB0707312D852432398C61BDD08C720@CP2PR80MB0707.lamprd80.prod.outlook.com>
<e772b0f8-57b1-67a7-2ef3-15e2b744bc45@gmail.com>
<CP2PR80MB07071E099387E61C92489A018C720@CP2PR80MB0707.lamprd80.prod.outlook.com>
<c730174f-9ec9-561a-d3ae-f736cd366c64@gmail.com>
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@gmail.com>
>> *Enviado:* segunda-feira, 27 de julho de 2020 18:27
>> *Para:* pgsql-admin@lists.postgresql.org
>> <pgsql-admin@lists.postgresql.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.g.johnston@gmail.com>
>>> <mailto:david.g.johnston@gmail.com>
>>> *Enviado:* segunda-feira, 27 de julho de 2020 17:17
>>> *Para:* Sidney Aloisio Ferreira Pryor <sidney@tjrj.jus.br>
>>> <mailto:sidney@tjrj.jus.br>
>>> *Cc:* pgsql-admin@lists.postgresql.org
>>> <mailto:pgsql-admin@lists.postgresql.org>
>>> <pgsql-admin@lists.postgresql.org>
>>> <mailto:pgsql-admin@lists.postgresql.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@tjrj.jus.br <mailto: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)
>>> (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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: How can i be certain autovacuum is causing reuse if table still grows
In-Reply-To: <ab846992-fa14-9071-07ca-157cef437c43@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox