| From: | Tomas Vondra <tomas(at)vondra(dot)me> |
|---|---|
| To: | ravi k <ravisql09(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Commit Latency |
| Date: | 2025-02-07 16:44:26 |
| Message-ID: | cf05efa5-c76d-4002-b214-d38424bb1665@vondra.me |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/7/25 14:00, ravi k wrote:
> Thanks for the suggestions!
>
> It looks the issue is happening at the time of wal creation, does
> wal_init_zero off is good option?
>
It's impossible to say if that option will help, considering how little
info about the system you provided. I suggest you start by answering the
questions you've been asked by me & Alvaro, explain why you concluded
it's related to WAL creation, etc.
regards
--
Tomas Vondra
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-02-07 17:00:52 | Re: How to perform a long running dry run transaction without blocking |
| Previous Message | Adrian Klaver | 2025-02-07 16:19:42 | Re: libc to libicu via pg_dump/pg_restore? |