| 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 06:41:11 |
| Message-ID: | 913378B8-0A7F-44A6-BF34-32BF58FC0876@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Apr 28, 2020, at 2:13 AM, Ashok kumar Mani <amani(at)accelaero(dot)com> wrote:
>
> Database is getting hung every day at 5AM. I found the below message from log file , Could you please help me , should I need to increase the max_wal_size value ?
Most likely. I would recommend enabling checkpoint logging to get a better understanding how often checkpoint are occurring, duration, and size in relation to buffer pool. Check for 'checkpoint starting’ and 'checkpoint complete’ in the PostgreSQL log files after enabling it.
log_checkpoints = on
What is shared_buffers, max_wal_size, and wal_buffers set to?
> Why it say “incomplete startup packet” in the log.
This should be benign.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashok kumar Mani | 2020-04-28 06:49:11 | RE: PostgreSQL DB checkpoint error! |
| Previous Message | Raj kumar | 2020-04-28 06:38:53 | pgbench data loading failure- tablepscace space or pg_wal mount space issue |