Re: pg_upgrade automatic testing - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade automatic testing
Date
Msg-id 1306350465.5609.3.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: pg_upgrade automatic testing  (Noah Misch <noah@leadboat.com>)
Responses Re: pg_upgrade automatic testing  (Robert Haas <robertmhaas@gmail.com>)
Re: pg_upgrade automatic testing  (Noah Misch <noah@leadboat.com>)
Re: pg_upgrade automatic testing  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.


Attachment

pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Next
From: Robert Haas
Date:
Subject: Re: use less space in xl_xact_commit patch