On Fri, Apr 3, 2020 at 9:40 AM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Fri, Apr 3, 2020 at 9:35 AM Dilip Kumar <dilipbal...@gmail.com> wrote: > > > > I have analyzed the WAL and there could be multiple reasons for the > > same. With small data, I have noticed that while inserting in the > > system index there was a Page Split and that created extra WAL. > > > > Thanks for the investigation. I think it is clear that we can't > expect the same WAL size even if we repeat the same operation unless > it is a fresh database. >
Attached find the latest patches. I have modified based on our discussion on user interface thread [1], ran pgindent on all patches, slightly modified one comment based on Dilip's input and added commit messages. I think the patches are in good shape. I would like to commit the first patch in this series tomorrow unless I see more comments or any other objections. The patch-2 might need to be rebased if the other related patch [2] got committed first and we might need to tweak a bit based on the input from other thread [1] where we are discussing user interface for it. [1] - https://www.postgresql.org/message-id/CAA4eK1%2Bo1Vj4Rso09pKOaKhY8QWTA0gWwCL3TGCi1rCLBBf-QQ%40mail.gmail.com [2] - https://www.postgresql.org/message-id/E1jKC4J-0007R3-Bo%40gemulon.postgresql.org -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
v14-0001-Add-infrastructure-to-track-WAL-usage.patch
Description: Binary data
v14-0002-Add-the-option-to-report-WAL-usage-in-EXPLAIN-an.patch
Description: Binary data
v14-0003-Allow-pg_stat_statements-to-track-WAL-usage-stat.patch
Description: Binary data
v14-0004-Allow-verbose-auto-vacuum-to-display-WAL-usage-s.patch
Description: Binary data
