CVS log for pgsql/src/bin/pg_dump/Attic/pg_upgrade

Up to [PostgreSQL CVS Repository] / pgsql / src / bin / pg_dump

Request diff between arbitrary revisions - Display revisions graphically

Keyword substitution: kv
Default branch: MAIN

Remove old pg_upgrade script, from Tom.

Fix recreation of sequence files for 7.2 also because of XID change from
beta4 to beta5.

Now works for 7.1 databases.

Now tested on 7.2->7.2 migration;  still disabled.  Need 7.1 testing now.

Keep it disabled.

Wow, it actually worked for the regression database.  More testing needed.

Sync up.

More testing, more cleanups.

pg_resetxlog specifies log location in hex;  more pg_upgrade testing
improvments.

More cleanups.

More updates for int8 sequence restoration.  Old dump file not required
anymore.

Handle int4-int8 sequence migration without full data dump.

More improvements using pg_resetxlog.  still disabled.

More pg_upgrade improvements.  Almost done, except for max transaction
setting.

More improvements;  still disabled.  (Don't panic.)

Update with new features.  Still disabled.

Remove clog copy.

Make improvements to pg_upgrade; is still disabled.

Replace implementation of pg_log as a relation accessed through the
buffer manager with 'pg_clog', a specialized access method modeled
on pg_xlog.  This simplifies startup (don't need to play games to
open pg_log; among other things, OverrideTransactionSystem goes away),
should improve performance a little, and opens the door to recycling
commit log space by removing no-longer-needed segments of the commit
log.  Actual recycling is not there yet, but I felt I should commit
this part separately since it'd still be useful if we chose not to
do transaction ID wraparound.

Updates for 7.1 branding.

Accept pg_group as well as pg_shadow data from dumpall script.
Rearrange handling of VACUUMs so that they are certain to be executed
as superuser not some random user; also, do not forget to vacuum
template1 itself.

1. miscadmin.h needs to include sys/types.h for a definition of pid_t

2. Regression tests fail for types int2 and int4 (which can easily be
fixed by adding entries to resultmap) aswell as float8 and geometry,
where floating point numbers appear to be rounded a little differently
than in your expected results (besides that I also need the positive
zeros file). I'm including a patch for the first 2, but I don't know
whether the latter two are actually a bug in postgres or a bug in the
OS or even allowed difference. I'm including my results for reference.

Rolf Grossmann

Fix pg_upgrade so it vacuums all databases.

pg_upgrade reminder.

Add a VACUUM command in hopes of making pg_upgrade usable again
in MVCC environment.  I do not trust this until Vadim says it's OK...

Re-enable pg_upgrade, after adding checks that the source
and target databases are of versions it knows about.

Cleanup

Disable pg_upgrade for 6.5.

I attach a patch for pg_upgrade.  This does two things:

1. check whether the program is being executed in $PGDATA/..  This is
   necessary if the data tree is not in the standard place, as is the
   case with the Debian distribution (because of Debian policy).

2. give a clearer error message if the dumped data structure fails to
   be loaded.

Oliver Elphick

cleanup

Fix from Tom Lane for pg_shadow in pg_upgrade

Fix pg_upgrade to notice if psql fails to execute the given
script, and not proceed with the update if so.
Also add #!/bin/sh header line.

Preserver pg_log and pg_variable in upgrade.  Cleanups.

Make old db directory configurable.

New pg_upgrade command.