summaryrefslogtreecommitdiff
path: root/databases/postgresql74-lib
AgeCommit message (Collapse)AuthorFilesLines
2005-07-15Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by makingjlam1-2/+2
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable that specifies all of the tools we need to build/run the package.
2005-06-30Update postgresql74* packages to 7.4.8.wiz1-1/+2
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-05-16Note that tar is required by this package.jlam1-1/+2
2005-03-19bump PKGREVISION for previous patch against CAN-2005-0247jschauma1-2/+2
2005-03-18PostgreSQL doesn't provide *.la files that include the libraryjlam1-1/+4
dependencies needed when linking PostgreSQL clients with -lpq. Define a BUILDLINK_LDADD.${PGSQL_TYPE} variable that lists the full set libraries that would be needed to link with -lpq.
2005-02-05Update postgresql74 to 7.4.7. This is security release only, fixesjdolecek1-2/+2
recently discovered LOAD vulnerability.
2004-12-18Patch Makefile.shlib so that when creating shared libraries, we don'tjlam1-2/+2
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-12-18Move the pg_config binary from -client to -lib. This fixes PR pkg/28685darcy2-3/+7
as well as the bulk build for py-postgresql. Note that the man page is still built and installed by -client. That's a trickier problem.
2004-12-02RECOMMENDED should be after DEPENDS.wiz1-2/+2
2004-12-02move >=7.4.3 to RECOMMENDED and allow for both postgresql74- andgrant1-2/+3
postgresql- pkgnames in DEPENDS so installations from earlier can still be used if you IGNORE_RECOMMENDED.
2004-11-28Remove pre-buildlink and post-buildlink as part of getting pkgsrc readyjlam1-2/+2
for pkgsrc-2004Q4. The "buildlink" phase was removed for the last branch, and this is the final cleanup. "post-buildlink" is now "post-wrapper".
2004-11-09Fix PLIST issue: unconditionally add ${WRKSRC}/src/backend to BUILD_DIRS.seb1-3/+1
It's only really needed on Darwin but building there on all platforms allows us to keep the same PLIST for all of them: buildling the backend results in two more include files to be installed. Per discussion with recht@ our dedicated postgresql74-* MAINTAINER ;)
2004-11-04Fix the build on Darwin.recht2-7/+23
2004-10-10Update PostgreSQL 7.4 packages to 7.4.5. Changes are mostly reliability fixes.jdolecek1-2/+2
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-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-08-16Bump PKGREVISION to 1 for the previous thread-safety change.recht1-1/+2
noted by wiz
2004-08-16Do not build with --enable-thread-safety on NetBSD. Currently, itrecht1-2/+3
causes more harm than good.
2004-07-24change pkgname to postgresql74* (from postgresql*)recht2-12/+12
2004-06-27update to 7.4.3recht3-9/+6
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-04-27Only enable-thread safety on systems which have native threads to avoidrecht1-3/+4
pulling in pth. Pointed out by seb@.
2004-04-25GNU tar 1.11.2 as seen in NetBSD 1.6.2 does not grok -T with -C likeseb1-2/+2
NetBSD pax-as-tar. So avoid using both...
2004-04-20Follow a suggestion by Josh Berkus (pgsql core team) and buildrecht2-3/+12
with --enable-thread-safety. Bump PKGREVISIONs accordingly (meta-pkg, -client, -lib).
2004-04-19Initial import of PostgreSQL 7.4.2recht5-0/+489
Libraries and headers. 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 package contains the database headers and libraries.