| From: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
|---|---|
| To: | 'Fujii Masao' <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "ikedamsh(at)oss(dot)nttdata(dot)com" <ikedamsh(at)oss(dot)nttdata(dot)com>, 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "magnus(at)hagander(dot)net" <magnus(at)hagander(dot)net> |
| Subject: | RE: New statistics for tuning WAL buffer size |
| Date: | 2020-10-02 01:05:44 |
| Message-ID: | TYAPR01MB2990369F7B09CD12075670CFFE310@TYAPR01MB2990.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-10-02 01:06:21 | Re: Disable WAL logging to speed up data loading |
| Previous Message | tsunakawa.takay@fujitsu.com | 2020-10-02 01:00:41 | RE: Should walsernder check correctness of WAL records? |