RE: New statistics for tuning WAL buffer size - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: New statistics for tuning WAL buffer size
Date
Msg-id TYAPR01MB29901792EA2A9FFE9307444FFE5C0@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to New statistics for tuning WAL buffer size  (Masahiro Ikeda <ikedamsh@oss.nttdata.com>)
Responses RE: New statistics for tuning WAL buffer size  (Masahiro Ikeda <ikedamsh@oss.nttdata.com>)
List pgsql-hackers
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
> It's important to provide the metrics for tuning the size of WAL buffers.
> For now, it's lack of the statistics how often processes wait to write WAL
> because WAL buffer is full.
>
> If those situation are often occurred, WAL buffer is too small for the workload.
> DBAs must to tune the WAL buffer size for performance improvement.

Yes, it's helpful to know if we need to enlarge the WAL buffer.  That's why our colleague HariBabu proposed the patch.
We'dbe happy if it could be committed in some form. 


> There are related threads, but those are not merged.
> https://www.postgresql.org/message-id/4FF824F3.5090407@uptime.jp
> https://www.postgresql.org/message-id/flat/CAJrrPGc6APFUGYNcPe4qcNx
> pL8gXKYv1KST%2BvwJcFtCSCEySnA%40mail.gmail.com

What's the difference between those patches?  What blocked them from being committed?


Regards
Takayuki Tsunakawa




pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Display individual query in pg_stat_activity
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Is it worth accepting multiple CRLs?