the non-development install.  Instead, use the LOAD mechanism to check
for the pg_upgrade_support shared object, like we do for other shared
object checks.

Backpatch to 9.1.

Report from Àlvaro

optimizer statistics so the cluster can be made available sooner.

	add ability to control permissions of created files
	have psql echo its queries for easier debugging
	output four separate log files, and delete them on success
	add -r/--retain option to keep log files after success
	make logs file append-only
	remove -g/-G/-l logging options
	sugggest tailing appropriate log file on failure
	enhance -v/--verbose behavior

right after we restore the schema (a common failure point), and right
before we do the link operation.

Per suggesgtions from Robert and ^!C^!^@lvaro

  -l, --logfile=FILENAME        log internal activity to file\n\

Idea from Peter.

have pg_upgrade allocate a maximum fixed size buffer for testing the
library file name, rather than base the allocation on the library name.

Backpatch to 9.1.

"plpython2" when upgrading from pre-PG 9.1.  Patch to head and 9.1.

Per report from Peter.

check cluster version numbers, and fix missing table alias.

All supported platforms support the C89 standard function atexit()
(SunOS 4 probably being the last one not to), and supporting both
makes the code clumsy.

This is the standard behavior but was forgotten in some places.

Instead, add a function pg_tablespace_location(oid) used to return
the same information, and do this by reading the symbolic link.

Doing it this way makes it possible to relocate a tablespace when the
database is down by simply changing the symbolic link.

preserve pg_class oids since PG 9.0.

Disabled for now because some build farm members with low resources
are not prepared to handle it.

It runs the regression tests, runs pg_upgrade on the populated
database, and compares the before and after dumps.  While not actually
a cross-version upgrade, this does detect omissions and bugs in the
involved tools from time to time.  It's also possible to do a
cross-version upgrade by manually supplying parameters.

allow upgrades of the same catalog version.  (Doesn't work for
tablespaces, as indicated by C comment.)

--- we were not using the scandir pattern filtering anyway.  This also
removes the scandir requirement in configure.

pattern, which is used on PG 9.1 and HEAD (but not pre-9.1).  Fixes
crash on Windows.

Backpatched to 9.1.

Reported by Mark Dilger

Kevin Grittner

cleanly handle old/new database mismatches.

'postgres' database.

new cluster.   vacuumdb, used by pg_upgrade, still has this dependency.

in the old cluster.

document its use for config-only directory installs.

directory, for config-only directory installs.  Only works for PG 9.2+
servers.