On Fri, May 29, 2015 at 3:08 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> It won't fix the fact that pg_upgrade is putting
> a wrong value into everybody's datminmxid field, which should really
> be addressed too, but I've been working on this for about three days
> virtually non-stop and I don't have the energy to tackle it right now.
> If anyone feels the urge to step into that breech, I think what it
> needs to do is: when upgrading from a 9.3-or-later instance, copy over
> each database's datminmxid into the corresponding database in the new
> cluster.
Bruce was kind enough to spend some time on IM with me this afternoon,
and I think this may actually be OK. What pg_upgrade does is:
1. First, put next-xid into the relminmxid for all tables, including
catalog tables. This is the correct behavior for upgrades from a
pre-9.3 release, and is correct for catalog tables in general.
2. Next, restoring the schema dump will set the relminmxid values for
all non-catalog tables to the value dumped from the old cluster. At
this point, everything is fine provided that we are coming from a
release 9.3 or newer. But if the old cluster is pre-9.3, it will have
dumped *zero* values for all of its relminmxid values; so all of the
user tables go from the correct value they had after step 1 to an
incorrect value.
3. Finally, if the old cluster is pre-9.3, repeat step 1, undoing the
damage done in step 2.
This is a bit convoluted, but I don't know of a reason why it
shouldn't work. Sorry for the false alarm.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company