Log message:
Changes 8.1.17:
* Prevent error recursion crashes when encoding conversion fails.
* Disallow "CREATE CONVERSION" with the wrong encodings for the
  specified conversion function.
* Fix core dump when to_char() is given format codes that are
  inappropriate for the type of the data argument.
* Fix decompilation of CASE WHEN with an implicit coercion.
* Fix possible misassignment of the owner of a TOAST table's rowtype.
* Clean up PL/pgSQL error status variables fully at block exit.
* Add MUST (Mauritius Island Summer Time) to the default list of
  known timezone abbreviations.

Log message:
Changes 8.1.16:
* Fix crash in autovacuum
  The crash occurs only after vacuuming a whole database for
  anti-transaction-wraparound purposes, which means that it occurs
  infrequently and is hard to track down.
* Improve handling of URLs in headline() function
* Improve handling of overlength headlines in headline() function
* Prevent possible Assert failure or misconversion if an encoding
  conversion is created with the wrong conversion function for the
  specified pair of encodings
* Avoid unnecessary locking of small tables in "VACUUM"
* Ensure that the contents of a holdable cursor don't depend on the
  contents of TOAST tables
* Fix uninitialized variables in "contrib/tsearch2"'s get_covers()
  function
* Fix configure script to properly report failure when unable to
  obtain linkage information for PL/Perl
* Make all documentation reference pgsql-bugs and/or pgsql-hackers as
  appropriate, instead of the now-decommissioned pgsql-ports and
  pgsql-patches mailing lists
* Update time zone data files to tzdata release 2009a (for Kathmandu
  and historical DST corrections in Switzerland, Cuba)

Log message:
Changes 8.1.15:
* 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.
* 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
* 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.
* Update time zone data files to tzdata release 2008i (for DST law
  changes in Argentina, Brazil, Mauritius, Syria)

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

Log message:
Changes 8.1.13:
* 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:
Add DESTDIR support.

Log message:
Add missing CONFLICTS with postgresql83-* packages.  Reported by ASau` on irc.

Log message:
Mark the main postgresql8[0-3] packages as meta packages.
This avoids the problems in PR 34914.

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

This is the last 8.1.X release for which the PostgreSQL community will
produce binary packages for Windows. Windows users are encouraged to
move to 8.2.X or later, since there are Windows-specific fixes in 8.2.X
that are impractical to back-port. 8.1.X will continue to be supported
on other platforms.

Log message:
* If PLIST_SRC is explicitly set to an empty value in a package Makefile,
  then automatically generate a PLIST that says "${PKGNAME} has no files".

* If PLIST_SRC and GENERATE_PLIST are not set in a package Makefile,
  and no PLIST files exist, then fail during the package build with
  PKG_FAIL_REASON.

* Remove "intentionally empty" PLISTs again.

Now, the easy way to say that a package installs no files is to just
add the following to the package Makefile:

	PLIST_SRC=	# empty