Re: pg_upgrade version checking questions
Christoph Berg <myon@debian.org>
From: Christoph Berg <myon@debian.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org, Tomasz Szypowski <tomasz.szypowski@gmail.com>
Date: 2019-03-22T09:45:40Z
Lists: pgsql-hackers
Re: Peter Eisentraut 2019-03-22 <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com> > I'm still in favor of defaulting --new-bindir appropriately. It seems > silly not to. We know where the directory is, we don't have to ask anyone. Fwiw I've been wondering why I have to pass that option every time I've been using pg_upgrade. +1 on making it optional/redundant. Christoph
Commits
-
pg_upgrade: Check version of target cluster binaries
- f06b1c598254 14.0 landed
-
pg_upgrade: Default new bindir to pg_upgrade location
- 959f6d6a1821 13.0 landed
-
pg_upgrade: Check all used executables
- 0befb4f31386 13.0 landed