Log message:
Changes 8.2.11:
* Fix GiST index corruption due to marking the wrong index entry
  "dead" after a deletion.
  This would result in index searches failing to find rows they
  should have found.
* Fix backend crash when the client encoding cannot represent a
  localized error message.
  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.
* Improve optimization of "expression" IN \ 
("expression-list") queries.
  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.
* Fix memory leak during rescan of a hashed aggregation plan.
* Ensure an error is reported when a newly-defined PL/pgSQL trigger
  function is invoked as a normal function.
* Prevent possible collision of relfilenode numbers when moving a
  table to another tablespace with "ALTER SET TABLESPACE".
  The command tried to re-use the existing filename, instead of
  picking one that is known unused in the destination directory.
* Fix incorrect tsearch2 headline generation when single query item
  matches first word of text.
* Fix improper display of fractional seconds in interval values when
  using a non-ISO datestyle in an "--enable-integer-datetimes" build.
* Ensure SPI_getvalue and SPI_getbinval behave correctly when the
  passed tuple and tuple descriptor have different numbers of columns.
* Fix ecpg's parsing of "CREATE ROLE".
* Fix recent breakage of pg_ctl restart.
* Ensure "pg_control" is opened in binary mode.
  pg_controldata and pg_resetxlog did this incorrectly, and so could
  fail on Windows.
* Update time zone data files to tzdata release 2008i (for DST law
  changes in Argentina, Brazil, Mauritius, Syria)

Log message:
Changes 8.2.10:
Bug-fix release, see HISTORY for details.

Log message:
Changes 8.2.9:
* Make pg_get_ruledef() parenthesize negative constants (Tom)
  Before this fix, a negative constant in a view or rule might be
  dumped as, say, -42::integer, which is subtly incorrect: it should
  be (-42)::integer due to operator precedence rules. Usually this
  would make little difference, but it could interact with another
  recent patch to cause PostgreSQL to reject what had been a valid
  "SELECT DISTINCT" view query. Since this could result in pg_dump
  output failing to reload, it is being treated as a high-priority
  fix. The only released versions in which dump output is actually
  incorrect are 8.3.1 and 8.2.7.
* Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom)
  This oversight could lead to problems if the aggregate was later
  involved in a "DROP OWNED" or "REASSIGN OWNED" operation.

Log message:
Changes 8.2.7:
* Fix character string comparison for Windows locales that consider
  different character combinations as equal
* Repair potential deadlock between concurrent "VACUUM FULL"
  operations on different system catalogs
* Fix longstanding "LISTEN"/"NOTIFY" race condition
* Disallow "LISTEN" and "UNLISTEN" within a prepared transaction
* Disallow dropping a temporary table within a prepared transaction
* Fix rare crash when an error occurs during a query using a hash
  index
* Fix memory leaks in certain usages of set-returning functions
* Fix input of datetime values for February 29 in years BC
* Fix "unrecognized node type" error in some variants of "ALTER
  OWNER"
* Ensure pg_stat_activity.waiting flag is cleared when a lock wait is
  aborted
* Fix handling of process permissions on Windows Vista
* More...

Log message:
Add an option for LDAP authentication as explained on
http://www.postgresql.org/docs/8.3/static/auth-methods.html#AUTH-LDAP

Log message:
Per the process outlined in revbump(1), perform a recursive revbump
on packages that are affected by the switch from the openssl 0.9.7
branch to the 0.9.8 branch. ok jlam@

Log message:
Changes 8.2.6:
This release contains a variety of fixes from 8.2.5, including fixes
for significant security issues.

Log message:
Changes 8.2.5:
* Prevent index corruption when a transaction inserts rows and then
  aborts close to the end of a concurrent "VACUUM" on the same table
* Fix ALTER DOMAIN ADD CONSTRAINT for cases involving domains over
  domains
* Make "CREATE DOMAIN ... DEFAULT NULL" work properly
* Fix some planner problems with outer joins, notably poor size
  estimation for t1 LEFT JOIN t2 WHERE t2.col IS NULL
* Allow the interval data type to accept input consisting only of
  milliseconds or microseconds
* Allow timezone name to appear before the year in timestamp input
* Fixes for GIN indexes used by "/contrib/tsearch2"
* Speed up rtree index insertion
* Fix excessive logging of SSL error messages
* Fix logging so that log messages are never interleaved when using
  the syslogger process
* Fix crash when log_min_error_statement logging runs out of memory
* Fix incorrect handling of some foreign-key corner cases
* Fix stddev_pop(numeric) and var_pop(numeric)
* Prevent "REINDEX" and "CLUSTER" from failing due to \ 
attempting to
  process temporary tables of other sessions
* Update the time zone database rules, particularly New Zealand's
  upcoming changes
* Windows socket and semaphore improvements
* Make "pg_ctl -w" work properly in Windows service mode
* Fix memory allocation bug when using MIT Kerberos on Windows
* Suppress timezone name (%Z) in log timestamps on Windows because of
  possible encoding mismatches
* Require non-superusers who use "/contrib/dblink" to use only
  password authentication, as a security measure
* Restrict "/contrib/pgstattuple" functions to superusers, for
  security reasons
* Do not let "/contrib/intarray" try to make its GIN opclass the
  default (this caused problems at dump/restore)

Log message:
Make it easier to build and install packages "unprivileged", where
the owner of all installed files is a non-root user.  This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.

(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
    unprivileged.mk.  These two variables are lists of other bmake
    variables that define package-specific users and groups.  Packages
    that have user-settable variables for users and groups, e.g. apache
    and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
    etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
    so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
    and ${UNPRIVILEGED_GROUP}.

(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.

Log message:
Changes 8.2.4:
* Support explicit placement of the temporary-table schema within
  search_path, and disable searching it for functions and operators
* Fix shared_preload_libraries for Windows by forcing reload in each
  backend
* Fix to_char() so it properly upper/lower cases localized day or
  month names
* "/contrib/tsearch2" crash fixes
* Require "COMMIT PREPARED" to be executed in the same database as
  the transaction was prepared in
* Allow "pg_dump" to do binary backups larger than two gigabytes on
  Windows
* New traditional (Taiwan) Chinese FAQ
* Prevent the statistics collector from writing to disk too
  frequently
* Fix potential-data-corruption bug in how "VACUUM FULL" handles
  "UPDATE" chains
* Fix bug in domains that use array types
* Fix "pg_dump" so it can dump a serial column's sequence using \ 
"-t"
  when not also dumping the owning table
* Planner fixes, including improving outer join and bitmap scan
  selection logic
* Fix possible wrong answers or crash when a PL/pgSQL function tries
  to RETURN from within an EXCEPTION block
* Fix PANIC during enlargement of a hash index
* Fix POSIX-style timezone specs to follow new USA DST rules