A dump/restore is not required for those running 8.2.X.
However, if you are upgrading from a version earlier than
8.2.7, see Section E.111.
Also, if you were running a previous 8.2.X release, it is
recommended to REINDEX all GiST
indexes after the upgrade.

We have addressed similar issues before, but it would
still fail if the "character has no
equivalent" message itself couldn't be converted.
The fix is to disable localization and send the plain ASCII
error message when we detect such a situation.

Fix possible crash when deeply nested functions are
invoked from a trigger (Tom)

Improve optimization of expressionIN (expression-list) queries (Tom, per an
idea from Robert Haas)

Cases in which there are query variables on the
right-hand side had been handled less efficiently in 8.2.x
and 8.3.x than in prior versions. The fix restores 8.1
behavior for such cases.

Fix mis-expansion of rule queries when a sub-SELECT appears in a function call in
FROM, a multi-row VALUES list, or a RETURNING list (Tom)

The usual symptom of this problem is an "unrecognized node type" error.

Fix memory leak during rescan of a hashed aggregation
plan (Neil)

Ensure an error is reported when a newly-defined
PL/pgSQL trigger function is invoked as a normal function
(Tom)

Prevent possible collision of relfilenode numbers when moving a table
to another tablespace with ALTER SET
TABLESPACE (Heikki)

The command tried to re-use the existing filename,
instead of picking one that is known unused in the
destination directory.