Re: pg_upgrade automatic testing
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Noah Misch <noah@leadboat.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-05-25T23:29:55Z
Lists: pgsql-hackers
On Wed, May 25, 2011 at 3:07 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On ons, 2011-04-27 at 18:14 -0400, Noah Misch wrote: >> Enthusiastic +1 for this concept. There's at least one rough edge: it fails if >> you have another postmaster running on port 5432. > > This has now been addressed: pg_upgrade accepts PGPORT settings. > Attached is a slightly updated patch runs the test suite with a port of > 65432, which you can override by setting PGPORT yourself. > > Anyway, is this something that people want in the repository? It's not > as polished as the pg_regress business, but it is definitely helpful. Is this going to result in using the built binaries with the installed libraries, a la Tom's recent complaint about the isolation tests? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company