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-20T22:13:03Z
Lists: pgsql-bugs
On Tue, Feb 20, 2018 at 7:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Claudio Freire <klaussfreire@gmail.com> writes: >>> Looking into this I also saw: >>> * set_frozenxids() >>> which makes a bit uncomfortable, but I can't quite put my finger on >>> why. > >> I looked into that one, it's not relevant to this case, since it's >> working on template1 (check the conn used there). > > Hm? Looks to me like it iterates through all the DBs in the cluster. > > regards, tom lane You're right. But IIUC it's called before restoring globals, so only postgres, template0 and template1 exist at that point.
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