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
Thanks for the suggestions!
It looks the issue is happening at the time of wal creation, does
wal_init_zero off is good option?
Best
On Wed, 5 Feb, 2025, 9:07 pm Álvaro Herrera,
wrote:
> Hello
>
> On 2025-Feb-05, Ramakrishna m wrote:
>
> > I have a system handling *300 TPS*, with resource usa
Hello
On 2025-Feb-05, Ramakrishna m wrote:
> I have a system handling *300 TPS*, with resource usage *below 10%*.
> However, I’m noticing *commit latency of around 200ms* for *1% of
> transactions*, occasionally spiking to *1 second*. Since there is no
> significant *I/O pressure*, I’m trying to
On Wed, 2025-02-05 at 15:48 +0530, Ramakrishna m wrote:
> I’m noticing commit latency of around 200ms for 1% of transactions,
> occasionally
> spiking to 1 second. Since there is no significant I/O pressure, I’m trying to
> identify what else might be causing this in PostgreSQL 16.
https://www.cy
I think the first thing you should do is verify the performance of the
storage, particularly how long it takes to do fsync. You didn't explain
what kind of storage or filesystem you're using, so hard to say.
It's not clear to me what "resource usage" means exactly, but the fsync
may be slow even w
