From: | Rijo Roy <rjo_roy(at)yahoo(dot)com> |
---|---|
To: | "a(dot)zakirov(at)postgrespro(dot)ru" <a(dot)zakirov(at)postgrespro(dot)ru>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Enabling autovacuum per table |
Date: | 2018-10-15 10:25:47 |
Message-ID: | 839519694.10529501.1539599147122@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yeah when age(relfrozenxid) goes beyond the limit Postgresql will invoke the autovacuum session to avoid a wraparound issue.. But here that's not the case..
Sent from Yahoo Mail on Android
On Mon, 15 Oct 2018 at 2:58 pm, Arthur Zakirov<a(dot)zakirov(at)postgrespro(dot)ru> wrote: On 10/15/18 11:01 AM, Rijo Roy wrote:
> Hello Experts,
>
> Is there any possibility for autovacuum to work on a user table if we set
> Alter table sometable set (autovacuum_enabled = true) ; even if the
> parameter autovacuum = off in Postgresql.conf
>
> I am using Postgresql 10 on Linux 6.9.
>
> According to me, it won't work without setting autovacuum = on except
> for Template0 database. What is your opinion?
I think you are right, autovacuum won't vacuum and analyze a table
without setting autovacuum = on. But PostgreSQL might want to force
vacuum if a table is at risk of wraparound.
--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Yuri Kanivetsky | 2018-10-15 10:31:04 | Re: Setting up continuous archiving |
Previous Message | Durgamahesh Manne | 2018-10-15 10:20:56 | Re: Regarding varchar max length in postgres |