Log message:
Make my life easier and push the tsearch2 patches out. The package itself
needs some more work though.

Log message:
Changes 8.1.5:
* Disallow aggregate functions in "UPDATE" commands, except within
  sub-SELECTs (Tom)
  The behavior of such an aggregate was unpredictable, and in 8.1.X
  could cause a crash, so it has been disabled. The SQL standard does
  not allow this either.
* Fix core dump when an untyped literal is taken as ANYARRAY
* Fix core dump in duration logging for extended query protocol when
  a "COMMIT" or "ROLLBACK" is executed
* Fix mishandling of AFTER triggers when query contains a SQL
  function returning multiple rows (Tom)
* Fix "ALTER TABLE ... TYPE" to recheck NOT NULL for USING clause
  (Tom)
* Fix string_to_array() to handle overlapping matches for the
  separator string
  For example, string_to_array('123xx456xxx789', 'xx').
* Fix to_timestamp() for AM/PM formats (Bruce)
* Fix autovacuum's calculation that decides whether "ANALYZE" is
  needed (Alvaro)
* Fix corner cases in pattern matching for psql's \d commands
* Fix index-corrupting bugs in /contrib/ltree (Teodor)
* Numerous robustness fixes in ecpg (Joachim Wieland)
* Fix backslash escaping in /contrib/dbmirror
* Minor fixes in /contrib/dblink and /contrib/tsearch2
* Efficiency improvements in hash tables and bitmap index scans (Tom)
* Fix instability of statistics collection on Win32 (Tom, Andrew)
* Fix statement_timeout to use the proper units on Win32 (Bruce)
  In previous Win32 8.1.X versions, the delay was off by a factor of
  100.
* Fixes for MSVC and Borland C++ compilers (Hiroshi Saito)
* Fixes for AIX and Intel compilers (Tom)

Log message:
Fix build on Darwin/MacOSX

Log message:
Update PostgreSQL to 7.3.15, 7.4.13, 8.0.8 and 8.1.4 respectively.

Common to all versions:
     * Change the server to reject invalidly-encoded multibyte characters
       in all cases (Tatsuo, Tom) While PostgreSQL has been moving in this
       direction for some time, the checks are now applied uniformly to
       all encodings and all textual input, and are now always errors not
       merely warnings. This change defends against SQL-injection attacks
       of the type described in CVE-2006-2313.
     * Reject unsafe uses of \' in string literals As a server-side
       defense against SQL-injection attacks of the type described in
       CVE-2006-2314, the server now only accepts '' and not \' as a
       representation of ASCII single quote in SQL string literals. By
       default, \' is  rejected  only  when  client_encoding is set to a
       client-only encoding (SJIS, BIG5, GBK, GB18030, or UHC), which is
       the scenario in which SQL injection is possible. A new
       configuration parameter backslash_quote is available  to  adjust
       this  behavior  when needed. Note that full security against
       CVE-2006-2314 may require client-side changes; the purpose of
       backslash_quote is in part to make it obvious that insecure clients
       are insecure.
     * Modify libpq's string-escaping routines to be aware of encoding
       considerations This  fixes  libpq-using applications for the
       security issues described in CVE-2006-2313 and CVE-2006-2314.
       Applications that use multiple PostgreSQL connections concurrently
       should migrate to PQescapeStringConn() and PQescapeByteaConn() to
       ensure that escaping is done correctly for the settings in use in
       each database connection. Applications that do string escaping
       "by hand" should be modified to rely on library routines instead.
     * Fix some incorrect encoding conversion functions win1251_to_iso,
       alt_to_iso, euc_tw_to_big5, euc_tw_to_mic, mic_to_euc_tw were all
       broken to varying extents.
     * Clean up stray remaining uses of \' in strings (Bruce, Jan)
     * Fix server to use custom DH SSL parameters correctly (Michael Fuhr)
     * Fix various minor memory leaks

Additionally for 7.4.13 and later:
     * Fix bug that sometimes caused OR'd index scans to miss rows they
       should have returned
     * Fix WAL replay for case where a btree index has been truncated
     * Fix SIMILAR TO for patterns involving | (Tom)
     * Fix for Bonjour on Intel Macs (Ashley Clark)

Additionally for 8.0.8 and 8.1.4:
     * Fix SELECT INTO and CREATE TABLE AS to create tables in the
       default tablespace, not the base directory (Kris Jurka)
     * Fix problem with password prompting on some Win32 systems (Robert
       Kinberg)

Additionally for 8.1.4:
     * Fix weak key selection in pgcrypto (Marko Kreen)
       Errors in fortuna PRNG reseeding logic could cause a predictable
       session key to be selected by pgp_sym_encrypt() in some cases.
       This only affects non-OpenSSL-using builds.
     * Make autovacuum visible in pg_stat_activity (Alvaro)
     * Disable full_page_writes (Tom)
       In certain cases, having full_page_writes off would cause crash
       recovery to fail. A proper fix will appear in 8.2; for now it's
       just disabled.
     * Various planner fixes, particularly for bitmap index scans and
       MIN/MAX optimization (Tom)
     * Fix incorrect optimization in merge join (Tom)
       Outer joins could sometimes emit multiple copies of unmatched
       rows.
     * Fix crash from using and modifying a plpgsql function in the same
       transaction
     * Improve qsort performance (Dann Corbit)
       Currently this code is only used on Solaris.
     * Improve pg_dump's handling of default values for domains
     * Fix pg_dumpall to handle identically-named users and groups
       reasonably (only possible when dumping from a pre-8.1 server) (Tom)
       The user and group will be merged into a single role with LOGIN
       permission. Formerly the merged role wouldn't have LOGIN
       permission, making it unusable as a user.
     * Fix pg_restore -n to work as documented (Tom)

Log message:
BUILD_USE_MSGFMT and USE_MSGFMT_PLURALS are obsolete.  Replace with
USE_TOOLS+=msgfmt.

Log message:
Over 1200 files touched but no revisions bumped :)

RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).

Log message:
Move pre-configure rule for Dragonfly into post-extract rule like
the other postgresql packages do. Fixes build of PL packages.

Log message:
s/wip/databases/ (hi uebayasi!)

Log message:
Initial import of PostgreSQL 8.1.3, from pkgsrc-wip.

This is an overview of new features in 8.1.0 against 8.0.x.  8.1.3 includes
many bug fixes since 8.1.0.  Please read documentation of the detailed changes
and procedure of data migration.

Overview

   Major changes in this release:

   Improve concurrent access to the shared buffer cache (Tom)
          Access to the shared buffer cache was identified as a
          significant scalability problem, particularly on multi-CPU
          systems. In this release, the way that locking is done in the
          buffer manager has been overhauled to reduce lock contention and
          improve scalability. The buffer manager has also been changed to
          use a "clock sweep" replacement policy.

   Allow index scans to use an intermediate in-memory bitmap (Tom)
          In previous releases, only a single index could be used to do
          lookups on a table. With this feature, if a query has "WHERE
          tab.col1 = 4 and tab.col2 = 9", and there is no multicolumn
          index on col1 and col2, but there is an index on col1 and
          another on col2, it is possible to search both indexes and
          combine the results in memory, then do heap fetches for only the
          rows matching both the col1 and col2 restrictions. This is very
          useful in environments that have a lot of unstructured queries
          where it is impossible to create indexes that match all possible
          access conditions. Bitmap scans are useful even with a single
          index, as they reduce the amount of random access needed; a
          bitmap index scan is efficient for retrieving fairly large
          fractions of the complete table, whereas plain index scans are
          not.

   Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
          Two-phase commit allows transactions to be "prepared" on several
          computers, and once all computers have successfully prepared
          their transactions (none failed), all transactions can be
          committed. Even if a machine crashes after a prepare, the
          prepared transaction can be committed after the machine is
          restarted. New syntax includes "PREPARE TRANSACTION" and
          "COMMIT/ROLLBACK PREPARED". A new system view pg_prepared_xacts
          has also been added.

   Create a new role system that replaces users and groups (Stephen Frost)
          Roles are a combination of users and groups. Like users, they
          can have login capability, and like groups, a role can have
          other roles as members. Roles basically remove the distinction
          between users and groups. For example, a role can:

          + Have login capability (optionally)
          + Own objects
          + Hold access permissions for database objects
          + Inherit permissions from other roles it is a member of

          Once a user logs into a role, she obtains capabilities of the
          login role plus any inherited roles, and can use "SET ROLE" to
          switch to other roles she is a member of. This feature is a
          generalization of the SQL standard's concept of roles. This
          change also replaces pg_shadow and pg_group by new role-capable
          catalogs pg_authid and pg_auth_members. The old tables are
          redefined as read-only views on the new role tables.

   Automatically use indexes for MIN() and MAX() (Tom)
          In previous releases, the only way to use an index for MIN() or
          MAX() was to rewrite the query as "SELECT col FROM tab ORDER BY
          col LIMIT 1". Index usage now happens automatically.

   Move /contrib/pg_autovacuum into the main server (Alvaro)
          Integrating autovacuum into the server allows it to be
          automatically started and stopped in sync with the database
          server, and allows autovacuum to be configured from
          "postgresql.conf".

   Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
          While PostgreSQL's MVCC locking allows "SELECT" to never be
          blocked by writers and therefore does not need shared row locks
          for typical operations, shared locks are useful for applications
          that require shared row locking. In particular this reduces the
          locking requirements imposed by referential integrity checks.

   Add dependencies on shared objects, specifically roles (Alvaro)
          This extension of the dependency mechanism prevents roles from
          being dropped while there are still database objects they own.
          Formerly it was possible to accidentally "orphan" objects by
          deleting their owner. While this could be recovered from, it was
          messy and unpleasant.

   Improve performance for partitioned tables (Simon)
          The new constraint_exclusion configuration parameter avoids
          lookups on child tables where constraints indicate that no
          matching rows exist in the child table.

          This allows for a basic type of table partitioning. If child
          tables store separate key ranges and this is enforced using
          appropriate "CHECK" constraints, the optimizer will skip child
          table accesses when the constraint guarantees no matching rows
          exist in the child table.