Re: pg_upgrade and materialized views
Claudio Freire <klaussfreire@gmail.com>
From: Claudio Freire <klaussfreire@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Date: 2018-02-21T00:22:06Z
Lists: pgsql-bugs
On Tue, Feb 20, 2018 at 8:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Claudio Freire <klaussfreire@gmail.com> writes: >>> Well, the attached script reproduces the issue. > > One thing this doesn't prove by itself is whether the use of > REFRESH MATERIALIZED VIEW CONCURRENTLY has any effect on the > situation. > > I poked at that a bit and noted that REFRESH MATERIALIZED VIEW > CONCURRENTLY doesn't seem to change the matview's relfrozenxid > at all, while a plain REFRESH advances the matview's relfrozenxid > to (more or less) the current xid counter. Probably the reason why only concurrently triggers the vacuum assertion is because only concurrently creates dead tuples. Vacuum won't check unless there are dead tuples, it skips all-visible pages.
Commits
-
Repair pg_upgrade's failure to preserve relfrozenxid for matviews.
- d3b0a23a2093 9.3.22 landed
- 9936f149952b 9.5.12 landed
- 66e203c851ab 9.6.8 landed
- 5ab5d21aaa0e 10.3 landed
- 38b41f182a66 11.0 landed
- 2d12c559335e 9.4.17 landed