| From: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
|---|---|
| To: | "rjo_roy(at)yahoo(dot)com" <rjo_roy(at)yahoo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Enabling autovacuum per table |
| Date: | 2018-10-15 09:27:59 |
| Message-ID: | 078d5504-ac33-ea9a-5ff5-85adfadbb1bc@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Laurenz Albe | 2018-10-15 09:40:31 | Re: Regarding varchar max length in postgres |
| Previous Message | Durgamahesh Manne | 2018-10-15 09:18:32 | Re: Regarding varchar max length in postgres |