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>, "ikedamsh@oss.nttdata.com" <ikedamsh@oss.nttdata.com>, 'Kyotaro Horiguchi' <horikyota.ntt@gmail.com>
Cc: "amit.kapila16@gmail.com" <amit.kapila16@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "magnus@hagander.net" <magnus@hagander.net>
Date: 2020-10-02T01:05:44Z
Lists: pgsql-hackers
From: Fujii Masao <masao.fujii@oss.nttdata.com>
> I think that we can improve that, for example, by storing backend id
> into WalSndCtl and making pg_stat_get_wal_senders() directly
> get the walsender's LocalPgBackendStatus with the backend id,
> rather than joining pg_stat_get_activity() and pg_stat_get_wal_senders().

Yeah, I had something like that in mind.  I think I'll take note of this as my private homework.  (Of course, anyone can do it.)


Regards
Takayuki Tsunakawa






Commits

  1. Add pg_stat_wal statistics view.