Re: New statistics for tuning WAL buffer size
От | Fujii Masao |
---|---|
Тема | Re: New statistics for tuning WAL buffer size |
Дата | |
Msg-id | 6d2f1822-e668-cf94-d5d1-d91414a5ddc5@oss.nttdata.com обсуждение исходный текст |
Ответ на | RE: New statistics for tuning WAL buffer size ("tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>) |
Ответы |
Re: New statistics for tuning WAL buffer size
|
Список | pgsql-hackers |
On 2020/08/21 12:08, tsunakawa.takay@fujitsu.com wrote: > From: Fujii Masao <masao.fujii@oss.nttdata.com> >> Just idea; it may be worth exposing the number of when new WAL file is >> created and zero-filled. This initialization may have impact on >> the performance of write-heavy workload generating lots of WAL. If this >> number is reported high, to reduce the number of this initialization, >> we can tune WAL-related parameters so that more "recycled" WAL files >> can be hold. > > Sounds good. Actually, I want to know how much those zeroing affected the transaction response times, but it may be thetarget of the wait event statistics that Imai-san is addressing. Maybe, so I'm ok if the first pg_stat_walwriter patch doesn't expose this number. We can extend it to include that later after we confirm that number is really useful. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: