Only documented change since previous pkgsrc revision is creation of
a sepearate jar file with compiled versions of the examples. Other
changes may exist.
*** Please note that a dump/restore is NOT required for those ***
*** running PostgreSQL 7.2. ***
Important changes from version 7.2 include:
Ensure that sequence counters do not go backwards after a crash (Tom)
Allow psql \connect to handle mixed case database and user names (Tom)
Return proper OID on command completion even with ON INSERT rules (Tom)
Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo)
Improve handling of multiple UNIONs with different lengths (Tom)
Fix for array subscripts handling (Tom)
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)
<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.
<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.
than "smart" mode so that the the database will always cleanly shutdown.
Previously, postgres would wait for clients to disconnect before stopping
the database process, which sometimes resulted in unclean shutdowns.
Problem noted by Curt Sampson <cjs@cynic.net> in private email.
I also convert this to use /etc/rc.subr if it is present.
in pkg/16075.
From DESCR:
Berkeley DB is an embeddable database system that supports keyed
access to data. The software is distributed in source code form,
and developers can compile and link the source code into a single
library for inclusion directly in their applications.
Changes since 2.2216 are missing, here is the changes from 1.2215 to 1.2216 :
* Portability changes for mSQL 3 and MySQL 4.
* Added transaction support for MySQL.
(Bob Lyons <lyons@nextrials.com>)
* dbd/dbdimp.c: Fixed MAXLENGTH warning; used to hint for
a not existing mysql_maxlength, which should read
mysql_max_length. (Paul DuBois <paul@snake.net>)
* Fixed installation problem when a directory was specified,
but did not exist. (Will Partain <partain@dcs.gla.ac.uk>)
* Fixed that mysql_errno wasn't used properly. (Chris Adams
<cmadams@hiwaay.net>)
* Fixed test suite problem, when user name and password
have been interpolated. (Bruno Hivert (LMC)
<lmcbrhi@lmc.ericsson.se>)
* mysql_insertid and mysql_affectedrows are no longer treated
as integers, but longs. Thanks to Michael G Schwern
<schwern@pobox.com>.
* Don't give warning for statement that is only a comment; This is
needed for mysqldump --disable-keys to work.
* Fixed unlikely caching bug when doing a join without keys. In this case
the last used field for a table always returned NULL.
* Added options to make LOAD DATA LOCAL INFILE more secure.
* Added --xml option to mysqldump for producing XML output.
* Changed to use autoconf 2.52 (from autoconf 2.13)
* Fixed bug in complicated join with const tables.
* Added internal safety checks for InnoDB.
* Some InnoDB variables was always shown in SHOW VARIABLES as OFF on
high-byte-first systems (like sparc).
* Fixed problem with one thread using an InnoDB table and another thread
doing an ALTER TABLE on the same table. Before that, mysqld could crash
with an assertion failure in row0row.c, line 474.
* Tuned the InnoDB SQL optimizer to favor more often index searches over
table scans. SELECT queries will now also generally run faster on all
platforms.
* If MySQL binlogging is used, InnoDB now prints after crash recovery the
latest MySQL binlog name and the offset InnoDB was able to recover to.
This is useful, for example, when resynchronizing a master and a slave
database in replication.
* Added better error messages to help in installation problems of
InnoDB tables.
* One can now recover also MySQL temporary tables which have become
orphaned inside the InnoDB tablespace.
* InnoDB now prevents a FOREIGN KEY declaration where the signedness is
not the same in the referencing and referenced integer columns.
* Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory
corruption and make mysqld to crash. Especially at risk was mysqldump,
because it calls frequently SHOW CREATE TABLE.
* If inserts to several tables containing an auto-inc column were wrapped
inside one LOCK TABLES, InnoDB asserted in lock0lock.c.
* In 3.23.47 we allowed several NULLS in a UNIQUE secondary index for an
InnoDB table. But CHECK TABLE was not relaxed: it reports the table as
corrupt. CHECK TABLE no longer complains in this situation.
* SHOW GRANTS now shows REFERENCES instead of REFERENCE.
* Don't give warning for statement that is only a comment; This is
needed for mysqldump --disable-keys to work.
* Fixed unlikely caching bug when doing a join without keys. In this case
the last used field for a table always returned NULL.
* Added options to make LOAD DATA LOCAL INFILE more secure.
* Added --xml option to mysqldump for producing XML output.
* Changed to use autoconf 2.52 (from autoconf 2.13)
* Fixed bug in complicated join with const tables.
* Added internal safety checks for InnoDB.
* Some InnoDB variables was always shown in SHOW VARIABLES as OFF on
high-byte-first systems (like sparc).
* Fixed problem with one thread using an InnoDB table and another thread
doing an ALTER TABLE on the same table. Before that, mysqld could crash
with an assertion failure in row0row.c, line 474.
* Tuned the InnoDB SQL optimizer to favor more often index searches over
table scans. SELECT queries will now also generally run faster on all
platforms.
* If MySQL binlogging is used, InnoDB now prints after crash recovery the
latest MySQL binlog name and the offset InnoDB was able to recover to.
This is useful, for example, when resynchronizing a master and a slave
database in replication.
* Added better error messages to help in installation problems of
InnoDB tables.
* One can now recover also MySQL temporary tables which have become
orphaned inside the InnoDB tablespace.
* InnoDB now prevents a FOREIGN KEY declaration where the signedness is
not the same in the referencing and referenced integer columns.
* Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory
corruption and make mysqld to crash. Especially at risk was mysqldump,
because it calls frequently SHOW CREATE TABLE.
* If inserts to several tables containing an auto-inc column were wrapped
inside one LOCK TABLES, InnoDB asserted in lock0lock.c.
* In 3.23.47 we allowed several NULLS in a UNIQUE secondary index for an
InnoDB table. But CHECK TABLE was not relaxed: it reports the table as
corrupt. CHECK TABLE no longer complains in this situation.
* SHOW GRANTS now shows REFERENCES instead of REFERENCE.
Changes since 0.51:
- tdspool now working for big endian systems
- Added some descriptive text to the PWD file
- EINTR handling during login (Kostya Ivanov)
- Added support for TLI style interfaces files (thanks Michael for explaining)
- Added 'text size' config option which changes textsize on connect
- Added preliminary TDS 8.0 support (no new datatypes supported though)
- Added 'emulate little endian' config flag
- Some TDS5 placeholder stuff. Not ready for primetime yet.
- Added support for new configuration format (freetds.conf)
- unixODBC now working
- Added support for nullable bits (BITN)
- checked in work on tds connection pooling server
- added preliminary userguide (James Lowden and me)
- a lot of work on ODBC driver, now works with PHP
- added config options for iodbc/unixodbc (unixODBC doesn't actually work yet)
- image -> char now works (verified with ctlib only)
- varbinary -> char now works with destlen of -1
- New config routines
- numeric problem with 7.0 fixed
- digit cutoff on numerics/floats fixed
As well as some bug fixes.
all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
Fixes part of pkg/15794 by Bernd Ernesti <bernd@arresum.inka.de>. This
wasn't actually a buildlink problem, but buildlink is flexible enough to
provide a solution.
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
