diff --git a/doc/src/sgml/release-8.2.sgml b/doc/src/sgml/release-8.2.sgml
index 0a9ee5031af..39bf5da2c9b 100644
--- a/doc/src/sgml/release-8.2.sgml
+++ b/doc/src/sgml/release-8.2.sgml
@@ -1,6 +1,313 @@
+
+ Release 8.2.22
+
+
+ Release Date
+ 2011-09-26
+
+
+
+ This release contains a variety of fixes from 8.2.21.
+ For information about new features in the 8.2 major release, see
+ .
+
+
+
+ The PostgreSQL> community will stop releasing updates
+ for the 8.2.X release series in December 2011.
+ Users are encouraged to update to a newer release branch soon.
+
+
+
+ Migration to Version 8.2.22
+
+
+ A dump/restore is not required for those running 8.2.X.
+ However, if you are upgrading from a version earlier than 8.2.14,
+ see the release notes for 8.2.14.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix multiple bugs in GiST index page split processing (Heikki
+ Linnakangas)
+
+
+
+ The probability of occurrence was low, but these could lead to index
+ corruption.
+
+
+
+
+
+ Avoid possibly accessing off the end of memory in ANALYZE>
+ (Noah Misch)
+
+
+
+ This fixes a very-low-probability server crash scenario.
+
+
+
+
+
+ Fix race condition in relcache init file invalidation (Tom Lane)
+
+
+
+ There was a window wherein a new backend process could read a stale init
+ file but miss the inval messages that would tell it the data is stale.
+ The result would be bizarre failures in catalog accesses, typically
+ could not read block 0 in file ...> later during startup.
+
+
+
+
+
+ Fix memory leak at end of a GiST index scan (Tom Lane)
+
+
+
+ Commands that perform many separate GiST index scans, such as
+ verification of a new GiST-based exclusion constraint on a table
+ already containing many rows, could transiently require large amounts of
+ memory due to this leak.
+
+
+
+
+
+ Fix performance problem when constructing a large, lossy bitmap
+ (Tom Lane)
+
+
+
+
+
+ Fix array- and path-creating functions to ensure padding bytes are
+ zeroes (Tom Lane)
+
+
+
+ This avoids some situations where the planner will think that
+ semantically-equal constants are not equal, resulting in poor
+ optimization.
+
+
+
+
+
+ Work around gcc 4.6.0 bug that breaks WAL replay (Tom Lane)
+
+
+
+ This could lead to loss of committed transactions after a server crash.
+
+
+
+
+
+ Fix dump bug for VALUES> in a view (Tom Lane)
+
+
+
+
+
+ Disallow SELECT FOR UPDATE/SHARE> on sequences (Tom Lane)
+
+
+
+ This operation doesn't work as expected and can lead to failures.
+
+
+
+
+
+ Defend against integer overflow when computing size of a hash table (Tom
+ Lane)
+
+
+
+
+
+ Fix portability bugs in use of credentials control messages for
+ peer> authentication (Tom Lane)
+
+
+
+
+
+ Fix typo in pg_srand48> seed initialization (Andres Freund)
+
+
+
+ This led to failure to use all bits of the provided seed. This function
+ is not used on most platforms (only those without srandom>),
+ and the potential security exposure from a less-random-than-expected
+ seed seems minimal in any case.
+
+
+
+
+
+ Avoid integer overflow when the sum of LIMIT> and
+ OFFSET> values exceeds 2^63 (Heikki Linnakangas)
+
+
+
+
+
+ Add overflow checks to int4> and int8> versions of
+ generate_series()> (Robert Haas)
+
+
+
+
+
+ Fix trailing-zero removal in to_char()> (Marti Raudsepp)
+
+
+
+ In a format with FM> and no digit positions
+ after the decimal point, zeroes to the left of the decimal point could
+ be removed incorrectly.
+
+
+
+
+
+ Fix pg_size_pretty()> to avoid overflow for inputs close to
+ 2^63 (Tom Lane)
+
+
+
+
+
+ Fix psql>'s counting of script file line numbers during
+ COPY> from a different file (Tom Lane)
+
+
+
+
+
+ Fix pg_restore>'s direct-to-database mode for
+ standard_conforming_strings> (Tom Lane)
+
+
+
+ pg_restore> could emit incorrect commands when restoring
+ directly to a database server from an archive file that had been made
+ with standard_conforming_strings> set to on>.
+
+
+
+
+
+ Fix write-past-buffer-end and memory leak in libpq>'s
+ LDAP service lookup code (Albe Laurenz)
+
+
+
+
+
+ In libpq>, avoid failures when using nonblocking I/O
+ and an SSL connection (Martin Pihlak, Tom Lane)
+
+
+
+
+
+ Improve libpq's handling of failures during connection startup
+ (Tom Lane)
+
+
+
+ In particular, the response to a server report of fork()>
+ failure during SSL connection startup is now saner.
+
+
+
+
+
+ Make ecpglib> write double> values with 15 digits
+ precision (Akira Kurosawa)
+
+
+
+
+
+ Apply upstream fix for blowfish signed-character bug (CVE-2011-2483)
+ (Tom Lane)
+
+
+
+ contrib/pg_crypto>'s blowfish encryption code could give
+ wrong results on platforms where char is signed (which is most),
+ leading to encrypted passwords being weaker than they should be.
+
+
+
+
+
+ Fix memory leak in contrib/seg> (Heikki Linnakangas)
+
+
+
+
+
+ Fix pgstatindex()> to give consistent results for empty
+ indexes (Tom Lane)
+
+
+
+
+
+ Allow building with perl 5.14 (Alex Hunsaker)
+
+
+
+
+
+ Update configure script's method for probing existence of system
+ functions (Tom Lane)
+
+
+
+ The version of autoconf we used in 8.3 and 8.2 could be fooled by
+ compilers that perform link-time optimization.
+
+
+
+
+
+ Fix assorted issues with build and install file paths containing spaces
+ (Tom Lane)
+
+
+
+
+
+ Update time zone data files to tzdata> release 2011i
+ for DST law changes in Canada, Egypt, Russia, Samoa, and South Sudan.
+
+
+
+
+
+
+
+
Release 8.2.21
@@ -1334,7 +1641,7 @@
- This fix prevents a PANIC if a VACUUM FULL> is cancelled
+ This fix prevents a PANIC if a VACUUM FULL> is canceled
after it's already committed its tuple movements, as well as transient
errors if a plain VACUUM> is interrupted after having
truncated the table.