Re: pg_upgrade and materialized views
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: pgsql-bugs@postgresql.org
Date: 2018-02-20T22:24:03Z
Lists: pgsql-bugs
Claudio Freire <klaussfreire@gmail.com> writes: > On Tue, Feb 20, 2018 at 7:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Hm? Looks to me like it iterates through all the DBs in the cluster. > You're right. But IIUC it's called before restoring globals, so only > postgres, template0 and template1 exist at that point. Hmm ... there's another call later, but that one only happens for pre-9.3 source DBs, which won't contain matviews nor partitioned tables. So maybe it's OK but I'm not quite sure, and even if it is OK it's only accidentally so. Be nice if the documentation for this code weren't so relentlessly bad --- the header comment for this function looks like it's telling you something useful, but it isn't even close to accurate. The comment right above the call in prepare_new_globals() seems unrelated to anyone's version of reality either. 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