| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | Ashok kumar Mani <amani(at)accelaero(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL DB checkpoint error! |
| Date: | 2020-04-28 07:01:47 |
| Message-ID: | 24FB3FC5-6F7E-4857-8555-C5F96E2F0105@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Apr 28, 2020, at 2:49 AM, Ashok kumar Mani <amani(at)accelaero(dot)com> wrote:
>
> Do I need to restart the postgresql service for log_checkpoints to make it active . I would like to enable this parameter temporarily and check it?
>
Nope, just get it in postgresql.conf and reload it. i.e. pg_ctl reload
>
> postgres=# show max_wal_size;
> max_wal_size
> --------------
> 2GB
> (1 row)
With the deletes, vacuum full, and reindex it is generating WALs at a rapid rate thus trigging another checkpoint given the 2GB size. The vacuum full and reindex are most likely causing Zabbix to be blocked.
I would rethink the vacuum full and reindex; before changing max_wal_size.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashok kumar Mani | 2020-04-28 07:06:31 | RE: PostgreSQL DB checkpoint error! |
| Previous Message | Rui DeSousa | 2020-04-28 06:50:23 | Re: PostgreSQL DB checkpoint error! |