On Fri, Apr 1, 2016 at 05:55:58PM -0400, Tom Lane wrote: > Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > > The reason for the failure is that pg_dump knows that 9.6 installations > > have the amtype column -- but on your older devel 9.6 install, it > > doesn't exist. To fix it we would have to compare catalog versions in > > pg_dump rather than major version, but we don't that anywhere. Anyway > > many upgrades could fail depending on other patches because of the same > > reason. I don't think we need to fix this. > > We've never expected pg_dump to be able to handle intermediate development > versions. It's enough of a maintenance burden that it knows how to dump > from all previous stable branches.
Pg_upgrade does handle catalog version changes. I don't think we ever anticipated catalog changes that would throw errors in pg_dump, which pg_upgrade relies on. I am saying that someday we might need pg_dump to track catalog versions. However, I am not even sure how pg_dump would check the catalog version. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
