From: | Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Why did my PostgreSQL tables double in size? |
Date: | 2023-11-20 08:22:04 |
Message-ID: | a57dd304-46ec-148c-8dc3-ddd9d413d8fa@cloud.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 11/20/23 05:22, Ron Johnson wrote:
> On Sun, Nov 19, 2023 at 5:24 PM Abdullah Ergin
> <abdullaherginwork(at)gmail(dot)com> wrote:
>
> During this period, I believe the unchecked increase in table size
> was due to the auto vacuum parameter being turned off. What should
> I do to prevent this from affecting the 12th month and beyond?
>
> Make sure not to comment out "autovacuum = on"?
>
> Create a cron job that regularly runs psql -Xtc "SHOW AUTOVACUUM", and
> sends an email if it's set to off?
And be sure to check no table has unexpectedly individual autovacuum
turned off :
select pg_class.oid::regclass,relkind, opts.* from pg_class JOIN LATERAL
pg_options_to_table(reloptions) opts ON (true) where relkind not in
('i','v','S') AND option_name ~* '.*autovacuum_enabled' AND
option_value='false'
From | Date | Subject | |
---|---|---|---|
Next Message | Abdullah Ergin | 2023-11-20 09:29:17 | Re: Why did my PostgreSQL tables double in size? |
Previous Message | 2023-11-20 06:40:50 | Re: GSSAPI authentication on Redhat8 and PostgreSQL15/16 |