Re: pg_upgrade and materialized views
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Victor Yegorov <vyegorov@gmail.com>,
Claudio Freire <klaussfreire@gmail.com>, pgsql-bugs@postgresql.org
Date: 2018-02-21T23:45:26Z
Lists: pgsql-bugs
Andres Freund <andres@anarazel.de> writes: > On 2018-02-21 10:08:12 -0500, Tom Lane wrote: >> Yeah, that does look suspiciously like a set of facts matching this >> problem :-( > I'd personally say ;), given that it's one less potentially data > corrupting bug to worry about ;). And it's one that can be fixed without > dataloss to boot. I've pushed a fix for this. I concluded after further study that there wasn't really much call for a unified notion of applicable relkinds, because actually what this code is dealing with is "relkinds that need preservation of dropped columns" and "relkinds that need preservation of relfrozenxid", both of which are somewhat different from "relkinds that have storage". What's really lacking is documentation, which I attempted to supply. For the code change proper, I did what you suggested and split the relfrozenxid hacking into an independent if-block. regards, tom lane
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