RE: New statistics for tuning WAL buffer size

tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>

From: "tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>
To: 'Fujii Masao' <masao.fujii@oss.nttdata.com>, Masahiro Ikeda <ikedamsh@oss.nttdata.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-08-21T02:53:42Z
Lists: pgsql-hackers
From: Fujii Masao <masao.fujii@oss.nttdata.com>
> I agree to expose the number of WAL write caused by full of WAL buffers.
> It's helpful when tuning wal_buffers size. Haribabu separated that number
> into two fields in his patch; one is the number of WAL write by backend,
> and another is by background processes and workers. But I'm not sure
> how useful such separation is. I'm ok with just one field for that number.

I agree with you.  I don't think we need to separate the numbers for foreground processes and background ones.  WAL buffer is a single resource.  So "Writes due to full WAL buffer are happening.  We may be able to boost performance by increasing wal_buffers" would be enough.


Regards
Takayuki Tsunakawa

Commits

  1. Add pg_stat_wal statistics view.