summaryrefslogtreecommitdiff
path: root/databases/postgresql74/distinfo
AgeCommit message (Collapse)AuthorFilesLines
2005-06-30Update postgresql74* packages to 7.4.8.wiz1-5/+4
Release Notes Release 7.4.8 Release date: 2005-05-09 This release contains a variety of fixes from 7.4.7, including several security-related issues. __________________________________________________________________ Migration to version 7.4.8 A dump/restore is not required for those running 7.4.X. However, it is one possible way of handling two significant security problems that have been found in the initial contents of 7.4.X system catalogs. A dump/initdb/reload sequence using 7.4.8's initdb will automatically correct these problems. The larger security problem is that the built-in character set encoding conversion functions can be invoked from SQL commands by unprivileged users, but the functions were not designed for such use and are not secure against malicious choices of arguments. The fix involves changing the declared parameter list of these functions so that they can no longer be invoked from SQL commands. (This does not affect their normal use by the encoding conversion machinery.) The lesser problem is that the "contrib/tsearch2" module creates several functions that are misdeclared to return internal when they do not accept internal arguments. This breaks type safety for all functions using internal arguments. It is strongly recommended that all installations repair these errors, either by initdb or by following the manual repair procedures given below. The errors at least allow unprivileged database users to crash their server process, and may allow unprivileged users to gain the privileges of a database superuser. While here, fix postgresql74-client package installation on 2.0 (broken -X), and avoid the need for gtar in tcl-postgresql74.
2005-03-17Backport patch fromjschauma1-1/+2
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.64.4.1&r2=1.64.4.2 to fix CAN-2005-0247 for postgresql74 Bump PKGREVISION on postgresql74-lib
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2005-02-05Update postgresql74 to 7.4.7. This is security release only, fixesjdolecek1-3/+3
recently discovered LOAD vulnerability.
2004-12-18Fix postgresql74-plperl so that it finds libperl.so at runtime. Thejlam1-2/+2
PostgreSQL configure/build infrastructure tries very hard to separate rpath flags from other LDFLAGS, which is completely unnecessary in pkgsrc since the wrapper scripts are smart enough to deal with it on their own. In this case, the GNU configure script was stripping out the rpath to libperl.so when setting perl_embed_ldflags, so modify the configure script to not do this. Also re-enable this package since it's possible to load the plperl.so language module again. I tested this with: createdb foo createlang -d foo plperl
2004-12-18I lost the checksum for the tarball in my last commit... add it back.jlam1-1/+3
2004-12-18Patch Makefile.shlib so that when creating shared libraries, we don'tjlam1-6/+4
only pass only the -L* LDFLAGS to the linker. This is correct for pkgsrc since the wrapper scripts take care of correctly passing the rpath info to the linker, so we don't need to filter those out. This allows plpgsql.so to find libintl.so if we are using the pkgsrc version of it. Bump the PKGREVISION of postgresql*-lib to 7.3.8nb1 and 7.4.6nb2. Link the postgres binary with the necessary flags to allow it to dlopen() modules that use pthreads[*]. This should allow postgres to open a plperl.so module built on a system with perl+threads. Bump the PKGREVISION of postgresql*-server to 7.3.8nb2 and 7.4.6nb2. [*] Note that this behavior can be tweaked globally by setting DLOPEN_REQUIRE_PTHREADS to "yes" or "no" in /etc/mk.conf.
2004-11-04Add back the sum for the hierarchical queries patch.recht1-1/+3
2004-10-25Update all postgresql74 packages to 7.4.6. This fixes following two issues:jdolecek1-6/+4
* A vulnerability exists due to the insecure creation of temporary files, which could possibly let a malicious user overwrite arbitrary files * Repair possible failure to update hint bits on disk Under rare circumstances this oversight could lead to "could not access transaction status" failures, which qualifies it as a potential-data-loss bug.
2004-10-21Add sum for patch file needed when compiling with PGSQL_USE_HIER=YESjonb1-1/+3
2004-10-10Add patches necessary to build PL/Python, based on information providedjdolecek1-1/+3
in PR pkg/23349 by Michal Pasternak.
2004-10-10Update PostgreSQL 7.4 packages to 7.4.5. Changes are mostly reliability fixes.jdolecek1-5/+3
Dump/restore is not necessary for 7.4.x users. Changes in 7.4.5: * Repair possible crash during concurrent btree index insertions This patch fixes a rare case in which concurrent insertions into a btree index could result in a server panic. No permanent damage would result, but it's still worth a re-release. The bug does not exist in pre-7.4 releases. Changes in 7.4.4: * Prevent possible loss of committed transactions during crash Due to insufficient interlocking between transaction commit and checkpointing, it was possible for transactions committed just before the most recent checkpoint to be lost, in whole or in part, following a database crash and restart. This is a serious bug that has existed since PostgreSQL 7.1. * Check HAVING restriction before evaluating result list of an aggregate plan * Avoid crash when session's current userID is deleted * Fix hashed crosstab for zero-rows case (Joe) * Force cache update after renaming a column in a foreign key * Pretty-print UNION queries correctly * Make psql handle \r\n newlines properly in COPY IN * pg_dump handled ACLs with grant options incorrectly * Fix thread support for OS X and Solaris * Updated JDBC driver (build 215) with various fixes * ECPG fixes * Translation updates (various contributors)
2004-07-24change pkgname to postgresql74* (from postgresql*)recht1-1/+3
2004-06-27update to 7.4.3recht1-5/+3
changes: * Fix temporary memory leak when using non-hashed aggregates (Tom) * ECPG fixes, including some for Informix compatibility (Michael) * Fixes for compiling with thread-safety, particularly Solaris (Bruce) * Fix error in COPY IN termination when using the old network protocol (ljb) * Several important fixes in pg_autovacuum (Matthew T. O'Connor) * Fix problem with reading tar-format dumps on NetBSD and BSD/OS (Bruce) * Several JDBC fixes * Fix ALTER SEQUENCE RESTART where last_value equals the restart value (Tom) * Repair failure to recalculate nested sub-selects (Tom) * Fix problems with non-constant expressions in LIMIT/OFFSET * Support FULL JOIN with no join clause, such as X FULL JOIN Y ON TRUE (Tom) * Fix another zero-column table bug (Tom) * Improve handling of non-qualified identifiers in GROUP BY clauses in sub-selects (Tom) * Do not generate "NATURAL CROSS JOIN" when decompiling rules (Tom) * Add checks for invalid field length in binary COPY (Tom) * Avoid locking conflict between ANALYZE and LISTEN/NOTIFY * Numerous translation updates (various contributors)
2004-06-25Adjust docdir in configure. It should fix broken postgresql74-contribtaca1-1/+2
package in bulk build.
2004-04-29Fix build for NetBSD > 1.6L < 2.0.recht1-2/+2
2004-04-20Follow a suggestion by Josh Berkus (pgsql core team) and buildrecht1-1/+2
with --enable-thread-safety. Bump PKGREVISIONs accordingly (meta-pkg, -client, -lib).
2004-04-19Initial import of PostgreSQL 7.4.2recht1-0/+7
meta-package PostgreSQL is a robust, next-generation, Object-Relational DBMS (ORDBMS), derived from the Berkeley Postgres database management system. While PostgreSQL retains the powerful object-relational data model, rich data types and easy extensibility of Postgres, it replaces the PostQuel query language with an extended subset of SQL. PostgreSQL is free and the complete source is available. This is the meta-package for the PostgreSQL database system.