Re: pg_upgrade and materialized views
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Victor Yegorov <vyegorov@gmail.com>, Claudio Freire <klaussfreire@gmail.com>, pgsql-bugs@postgresql.org
Date: 2018-02-21T23:49:43Z
Lists: pgsql-bugs
On 2018-02-21 18:45:26 -0500, Tom Lane wrote: > I've pushed a fix for this. Thanks for this work, the new comments indeed make this much clearer! Wonder if we should include a comment in the release notes that possible occurances of the problem can be fixed with REFRESH? Perhaps that's obvious? I also wonder if there's a chance that this can result in wrong query results without getting errors, once the xids appears to be from the future - if so, should we ask people to refresh matviews if they're older than pg_upgrade? Greetings, Andres Freund
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