Here is a new migration file for 1.02.1. It includes the 'copy'
change and a script to convert old ASCII files.

Note: The following notes are for the benefit of users
who want to migrate databases from Postgres95 1.01 and 1.02 to Postgres95 1.02.1.

If you are starting afresh with Postgres95 1.02.1 and do not need to migrate
old databases, you do not need to read any further.

In order to upgrade older Postgres95 version 1.01 or 1.02 databases to
version 1.02.1, the following steps are required:

Start up a new 1.02.1 postmaster

Add the new built-in functions and operators of 1.02.1 to 1.01
or 1.02 databases. This is done by running the new 1.02.1 server
against your own 1.01 or 1.02 database and applying the queries
attached at the end of the file. This can be done easily through
psql. If your 1.01 or 1.02 database is
named testdb and you have cut the commands
from the end of this file and saved them in addfunc.sql:

% psql testdb -f addfunc.sql

Those upgrading 1.02 databases will get a warning when executing
the last two statements in the file because they are already
present in 1.02. This is not a cause for concern.

If you are trying to reload a pg_dump or text-mode, copy tablename to stdout generated with a previous
version, you will need to run the attached sed script on the ASCII file before loading it into
the database. The old format used '.' as end-of-data, while '\.' is
now the end-of-data marker. Also, empty strings are now loaded in
as '' rather than NULL. See the copy manual page for full
details.

sed 's/^\.$/\\./g' <in_file >out_file

If you are loading an older binary copy or non-stdout copy, there is no end-of-data character,
and hence no conversion necessary.

Submit correction

If you see anything in the documentation that is not correct, does not match
your experience with the particular feature or requires further clarification,
please use
this form
to report a documentation issue.