summaryrefslogtreecommitdiff
path: root/databases/tcl-postgresql74
AgeCommit message (Collapse)AuthorFilesLines
2006-12-27As discussed on tech-pkg, remove PostgreSQL 7.4.joerg5-61/+0
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-06-16Fixed pkglint warnings, including some copy&paste errors.rillig2-15/+15
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-02-21Update PostgreSQL 7.4.x to 7.4.12. Take maintainership.joerg1-2/+1
The fix for locales and plperl in 7.4.11 might make an REINDEX necessary. Changes from 7.4.8 to 7.4.9: - Fix error that allowed VACUUM to remove ctid chains too soon, and add more checking in code that follows ctid links - Fix CHAR() to properly pad spaces to the specified length when using a multiple-byte character set (Yoshiyuki Asaba) - Fix the sense of the test for read-only transaction in COPY - 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 - 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 - Don't try to open more than max_files_per_process files during postmaster startup - Various memory leakage fixes - Various portability improvements - Fix PL/PgSQL to handle var := var correctly when the variable is of pass-by-reference type - Update contrib/tsearch2 to use current Snowball code Changes from 7.4.9 to 7.4.10: - Fix race condition in transaction log management - Prevent failure if client sends Bind protocol message when current transaction is already aborted - /contrib/ltree fixes (Teodor) - AIX and HPUX compile fixes (Tom) - Fix longstanding planning error for outer joins - Prevent core dump in pg_autovacuum when a table has been dropped Changes from 7.4.10 to 7.4.11: - Fix for protocol-level Describe messages issued outside a transaction or in a failed transaction (Tom) - Fix character string comparison for locales that consider different character combinations as equal, such as Hungarian (Tom) - Set locale environment variables during postmaster startup to ensure that plperl won't change the locale later - Fix longstanding bug in strpos() and regular expression handling in certain rarely used Asian multi-byte character sets (Tatsuo) - Fix bug in /contrib/pgcrypto gen_salt, which caused it not to use all available salt space for MD5 and XDES algorithms (Marko Kreen, Solar Designer) - Fix /contrib/dblink to throw an error, rather than crashing, when the number of columns specified is different from what's actually returned by the query (Joe) Changes from 7.4.11 to 7.4.12: - Fix potential crash in SET SESSION AUTHORIZATION (CVE-2006-0553) - Fix bug with row visibility logic in self-inserted rows (Tom) - Fix race condition that could lead to "file already exists" errors during pg_clog file creation (Tom) - Properly check DOMAIN constraints for UNKNOWN parameters in prepared statements (Neil) - Fix to allow restoring dumps that have cross-schema references to custom operators (Tom) - Portability fix for testing presence of finite and isinf during configure (Tom)
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-2/+4
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-2/+2
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-4/+4
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-12-02Merge DragonFly pre-configure merging back into Makefile.common'sjoerg1-14/+1
post-extract.
2005-12-02DragonFly support.joerg1-1/+14
2005-06-30Update postgresql74* packages to 7.4.8.wiz1-3/+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 gtar is required by the package.jlam1-1/+2
2005-04-29Tcl interface to PostgreSQL, including front-end clients and a loadablegson5-0/+59
shared object for Tcl clients. This is based on, and almost identical to, the tcl-postgresql73 package, but for PostgreSQL 7.4 rather than 7.3.