summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2020-04-04 10:02:08 +0530
committerAmit Kapila <akapila@postgresql.org>2020-04-04 10:02:08 +0530
commitdf3b181499b40523bd6244a4e5eb554acb9020ce (patch)
tree520cb5eee0f4c1404face0b9df8be2c68158a7d2 /src/backend/access/gist/gistxlog.c
parent0588ee63aa2d8c5765d086991555cd9acdd4d86f (diff)
downloadpostgresql-df3b181499b40523bd6244a4e5eb554acb9020ce.tar.gz
Add infrastructure to track WAL usage.
This allows gathering the WAL generation statistics for each statement execution. The three statistics that we collect are the number of WAL records, the number of full page writes and the amount of WAL bytes generated. This helps the users who have write-intensive workload to see the impact of I/O due to WAL. This further enables us to see approximately what percentage of overall WAL is due to full page writes. In the future, we can extend this functionality to allow us to compute the the exact amount of WAL data due to full page writes. This patch in itself is just an infrastructure to compute WAL usage data. The upcoming patches will expose this data via explain, auto_explain, pg_stat_statements and verbose (auto)vacuum output. Author: Kirill Bychik, Julien Rouhaud Reviewed-by: Dilip Kumar, Fujii Masao and Amit Kapila Discussion: https://postgr.es/m/CAB-hujrP8ZfUkvL5OYETipQwA=e3n7oqHFU=4ZLxWS_Cza3kQQ@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions