Log message:
If we're passing through MAKEFLAGS variables whose values may contain
spaces, use the :Q modifier instead of double-quoting the value.  This
avoids breakage when executing the just-in-time su targets.

Log message:
cosmetics: use ${PYSITELIB}

Log message:
s/netbsd.org/NetBSD.org/

Log message:
Build py-postgresql from the postgresql 7.3.2 tarball. PKGREVISION++
Remove files and patches in the py-postgresql directory and add necessary
ones in the postgresql directory.

Log message:
Decouple py-postgresql from the postgresql build infrastructure and make
this package build standalone.  py-postgresql uses it's own version
numbering and really doesn't have much to do with the rest of the
postgresql packages.

Log message:
postgresql-7.2.3 contains PyGreSQL-3.3, so reflect this in the name

Log message:
Update py-postgresql to build using the postgresql-7.2.3 sources.

Log message:
buildlink1 -> buildlink2.

Log message:
Strip the ".buildlink" from the names of the python application and
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks.  Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.

Log message:
Update postgresql and related packages to 7.2.  Thanks to Michael Graff
<explorer@flame.org> for most of the work on this update.

Pkgsrc changes from the previous version include removing Makefile.ssl and
some patches that have been integrated into this release of PostgreSQL.  We
leave open the question of when to byte-compile the Python modules for the
PyGreSQL interface and just do it as before, although we should consider
doing the compilation as a post-install step to ensure that the timestamps
are correct.  We also reorder some lines in the Makefile to include
Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY)
as they may possibly trigger different portions of Makefile.common.

*** Please note that a dump/restore is required to migrate an existing ***
*** PostgreSQL installation to 7.2.                                    ***

Major changes from version 7.1.3 are geared toward improving use in
high-volume applications and include:

   VACUUM
	   Vacuuming no longer locks tables, thus allowing normal user access
           during the vacuum. A new "VACUUM FULL" command does old-style
           vacuum by locking the table and shrinking the on-disk copy of the
           table.

   Transactions
           There is no longer a problem with installations that exceed four
           billion transactions.

   OID's
           OID's are now optional. Users can now create tables without OID's
           for cases where OID usage is excessive.

   Optimizer
           The system now computes histogram column statistics during
           "ANALYZE", allowing much better optimizer choices.

   Security
           A new MD5 encryption option allows more secure storage and
           transfer of passwords. A new Unix-domain socket authentication
           option is available on Linux and BSD systems. PAM authentication
           is also available.

   Statistics
           Administrators can use the new table access statistics module to
           get fine-grained information about table and index usage.