Horton

Re: Statistics import and export: difference in statistics of materialized view dumped

Jeff Davis <pgsql@j-davis.com>

View thread View on postgr.es
From: Jeff Davis <pgsql@j-davis.com>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>, Corey Huinker <corey.huinker@gmail.com>
Date: 2025-03-28T23:20:58Z
Lists: pgsql-hackers 
On Fri, 2025-03-28 at 14:53 +0530, Ashutosh Bapat wrote:
> When I applied v1 it didn't pass.

I applied v1 on top of master as of March 15 (771ba90298), and then
took your two changes adding the tests, and it passed.

Version v2j is just rebased forward, which involved a trivial merge
conflict.

> But applying v2j-0003, the test passes.

Great.

> It feels like we can simplify this as: REFRESH MATERIALIZED VIEW
> replaces storage and resets the stats hence the Matview stats should
> be printed after printing REFRESH MATERIALIZED VIEW command in
> SECTION_POST_DATA. Also the materialized view ... . Hence the section
> may be updated later for materialized views.

Done, with a few modifications. Hopefully it's simpler.


Tom suggested that there may be other dependency problems lurking, but
I believe the patch is an improvement, so I committed it now to unblock
your work.

Regards,
	Jeff Davis

Commits

  1. Matview statistics depend on matview data.