in the 2.3.x series. This is a major update over version 2.2.x, and
changes include:
* Slapd(8) enhancements
- Updated slapd "overlay" interface, and several
example (and mostly experimental) overlays.
- Updated LDAP "sync" Engine with replication support,
provider now an "overlay"
- Numerous access control enhancements, including
experimental "don't disclose on error" capability
- Configuration backend
* LDAPv3 extensions, including:
- LDAP Password Policy
- LDAP Component Matching (requires OpenLDAP snacc)
- LDAP Modify Increment
changes:
* Switched back to old implementation of
ldap.schema.tokenizer.split_tokens() since the new one
had a bug which deletes the spaces from DESC
* ldap.INSUFFICIENT_ACCESS is now ignored in
ldap.ldapobject.LDAPObject.search_subschemasubentry_s()
4.3.28, so there are no API changes, and applications may be upgraded
by relinking against db4-4.3.29. We stop pretending to support a
"java" package option since we never even bothered with handling the
PLIST differences. Changes from version 4.3.28 include:
* The on-disk log format has changed.
* Add support for lightweight, transactionally protected Sequence
Number generation.
* Add support for Degree 2 isolation.
* Add election generation information to replication to support Paxos
compliance.
* A huge number of bug fixes, including eliminating some instances of
application deadlock and memory leak fixes.
* Some minor performance enhancements.
previous 8.0.x release, no dump-and-restore is necessary. Changes
from version 8.0.3 include:
postgresql80-client:
- Clarify comment for pgsql-hier-query option to note that it is
considered buggy by PostgreSQL developers.
* Make psql -f filename return a nonzero exit code when opening the
file fails
* Change pg_dump to handle inherited check constraints more reliably
postgresql80-server:
* Fix error that allowed "VACUUM" to remove ctid chains too soon, and
add more checking in code that follows ctid links
This fixes a long-standing problem that could cause crashes in very
rare circumstances.
* Fix CHAR() to properly pad spaces to the specified length when
using a multiple-byte character set (Yoshiyuki Asaba)
In prior releases, the padding of CHAR() was incorrect because it
only padded to the specified number of bytes without considering
how many characters were stored.
* Force a checkpoint before committing "CREATE DATABASE"
This should fix recent reports of "index is not a btree" failures
when a crash occurs shortly after "CREATE DATABASE".
* Fix the sense of the test for read-only transaction in "COPY"
The code formerly prohibited "COPY TO", where it should prohibit
"COPY FROM".
* Handle consecutive embedded newlines in "COPY" CSV-mode input
* Fix date_trunc(week) for dates near year end
* Fix planning problem with outer-join ON clauses that reference only
the inner-side relation
* Further fixes for x FULL JOIN y ON true corner cases
* Fix overenthusiastic optimization of x IN (SELECT DISTINCT ...) and
related cases
* Fix mis-planning of queries with small LIMIT values due to poorly
thought out "fuzzy" cost comparison
* Make array_in and array_recv more paranoid about validating their
OID parameter
* Fix missing rows in queries like UPDATE a=... WHERE a... with GiST
index on column a
* Improve robustness of datetime parsing
* Improve checking for partially-written WAL pages
* Improve robustness of signal handling when SSL is enabled
* Improve MIPS and M68K spinlock code
* Don't try to open more than max_files_per_process files during
postmaster startup
* Various memory leakage fixes
* Various portability improvements
* Update timezone data files
* Fix PL/PgSQL to handle var := var correctly when the variable is of
pass-by-reference type
postgresql80-plperl:
* Fix PL/Perl %_SHARED so it's actually shared
QDBM is an embeded database library compatible with GDBM and NDBM. It
features hash database and B+ tree database and is developed referring
to GDBM for the purpose of the following three points: higher
processing speed, smaller size of a database file, and simpler API.
This package includes APIs for C, C++, and Java. CGI scripts are also
contained. APIs for Perl and Ruby should be installed with a source
package.
Main changes since 0.61 besides general bug fixes:
* BCP support for db-lib and ct-lib
* many ODBC fixes
* added support for TDS 8.0
* iconv changes (better collation, improve error reporting)
2005 September 24 (3.2.7)
* GROUP BY now considers NULLs to be equal again, as it should
* Now compiles on Solaris and OpenBSD and other Unix variants that lack the
fdatasync() function
* Now compiles on MSVC++6 again
* Fix uninitialized variables causing malfunctions for various obscure queries
* Correctly compute a LEFT OUTER JOINs that is constrained on the left table only
2005 September 17 (3.2.6)
* Fix a bug that can cause database corruption if a VACUUM (or autovacuum) fails
and is rolled back on a database that is larger than 1GiB
* LIKE optiization now works for columns with COLLATE NOCASE
* ORDER BY and GROUP BY now use bounded memory
* Added support for COUNT(DISTINCT expr)
* Change the way SUM() handles NULL values in order to comply with the SQL standard
* Use fdatasync() instead of fsync() where possible in order to speed up commits
slightly
* Use of the CROSS keyword in a join turns off the table reordering optimization
* Added the experimental and undocumented EXPLAIN QUERY PLAN capability
* Use the unicode API in windows
2005 August 27 (3.2.5)
* Fix a bug effecting DELETE and UPDATE statements that changed more than 40960
rows.
* Change the makefile so that it no longer requires GNUmake extensions
* Fix the --enable-threadsafe option on the configure script
* Fix a code generator bug that occurs when the left-hand side of an IN operator is
constant and the right-hand side is a SELECT statement
* The PRAGMA synchronous=off statement now disables syncing of the master journal
file in addition to the normal rollback journals
2005 August 24 (3.2.4)
* Fix a bug introduced in the previous release that can cause a segfault while
generating code for complex WHERE clauses.
* Allow floating point literals to begin or end with a decimal point.
2005 August 21 (3.2.3)
* Added support for the CAST operator
* Tcl interface allows BLOB values to be transferred to user-defined functions
* Added the "transaction" method to the Tcl interface
* Allow the DEFAULT value of a column to call functions that have constant operands
* Added the ANALYZE command for gathering statistics on indices and using those
statistics when picking an index in the optimizer
* Remove the limit (formerly 100) on the number of terms in the WHERE clause
* The right-hand side of the IN operator can now be a list of expressions instead
of just a list of constants
* Rework the optimizer so that it is able to make better use of indices
* The order of tables in a join is adjusted automatically to make better use of
indices
* The IN operator is now a candidate for optimization even if the left-hand side is
not the left-most term of the index. Multiple IN operators can be used with the
same index.
* WHERE clause expressions using BETWEEN and OR are now candidates for optimization
* Added the "case_sensitive_like" pragma and the SQLITE_CASE_SENSITIVE_LIKE
compile-time option to set its default value to "on".
* Use indices to help with GLOB expressions and LIKE expressions too when the
case_sensitive_like pragma is enabled
* Added support for grave-accent quoting for compatibility with MySQL
* Improved test coverage
Functionality added or changed:
* Added the mysql_get_client_version C API function to the embedded
server library. (It was present in the regular client library but
inadvertently omitted from the embedded library.)
Please see http://dev.mysql.com/doc/mysql/en/news-4-0-26.html
for more information.
and referrals are used together (http://secunia.com/advisories/15906/)
mostly from Adrian Portelli, tested by me
(The most recent version 242 kills the system completely if the LDAP
server is not running -- endless connection retries.)
of "ldopts" used to link in the embedded perl interpreter. This fixes
PR pkg/31293.
The PostgreSQL configure code tries to be extra-clever with only using
its own logic for determining which directories to add to the rpath.
However, we don't really need PostgreSQL's configure to do this since
the Perl config already provides the full set of flags for linking,
including the appropriate rpath flags, and the rpaths flags determined
by Perl (at least in pkgsrc) are guaranteed to match the ones needed
PostgreSQL to link the plperl.so module.
Bump the PKGREVISION of databases/postgresql80-plperl to 1.
