Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql73
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Remove PostgreSQL 7.3 and pgaccess.
Pullup ticket 1680 - requested by joerg
security updates for postgresql
Revisions pulled up:
- pkgsrc/databases/postgresql73/Makefile.common 1.19
- pkgsrc/databases/postgresql73/distinfo 1.13
- pkgsrc/databases/postgresql73-docs/PLIST 1.7
- pkgsrc/databases/postgresql74/Makefile.common 1.36
- pkgsrc/databases/postgresql74/distinfo 1.21
- pkgsrc/databases/postgresql74-docs/PLIST 1.6
- pkgsrc/databases/postgresql80/Makefile.common 1.23
- pkgsrc/databases/postgresql80/distinfo 1.13
- pkgsrc/databases/postgresql80-client/PLIST 1.11
- pkgsrc/databases/postgresql81/Makefile.common 1.6
- pkgsrc/databases/postgresql81/distinfo 1.2
- pkgsrc/databases/postgresql81-client/PLIST 1.2
Module Name: pkgsrc
Committed By: joerg
Date: Fri May 26 17:47:58 UTC 2006
Modified Files:
pkgsrc/databases/postgresql73: Makefile.common distinfo
pkgsrc/databases/postgresql73-docs: PLIST
pkgsrc/databases/postgresql74: Makefile.common distinfo
pkgsrc/databases/postgresql74-docs: PLIST
pkgsrc/databases/postgresql80: Makefile.common distinfo
pkgsrc/databases/postgresql80-client: PLIST
pkgsrc/databases/postgresql81: Makefile.common distinfo
pkgsrc/databases/postgresql81-client: PLIST
Log Message:
Update PostgreSQL to 7.3.15, 7.4.13, 8.0.8 and 8.1.4 respectively.
Common to all versions:
* Change the server to reject invalidly-encoded multibyte characters
in all cases (Tatsuo, Tom) While PostgreSQL has been moving in this
direction for some time, the checks are now applied uniformly to
all encodings and all textual input, and are now always errors not
merely warnings. This change defends against SQL-injection attacks
of the type described in CVE-2006-2313.
* Reject unsafe uses of \' in string literals As a server-side
defense against SQL-injection attacks of the type described in
CVE-2006-2314, the server now only accepts '' and not \' as a
representation of ASCII single quote in SQL string literals. By
default, \' is rejected only when client_encoding is set to a
client-only encoding (SJIS, BIG5, GBK, GB18030, or UHC), which is
the scenario in which SQL injection is possible. A new
configuration parameter backslash_quote is available to adjust
this behavior when needed. Note that full security against
CVE-2006-2314 may require client-side changes; the purpose of
backslash_quote is in part to make it obvious that insecure clients
are insecure.
* Modify libpq's string-escaping routines to be aware of encoding
considerations This fixes libpq-using applications for the
security issues described in CVE-2006-2313 and CVE-2006-2314.
Applications that use multiple PostgreSQL connections concurrently
should migrate to PQescapeStringConn() and PQescapeByteaConn() to
ensure that escaping is done correctly for the settings in use in
each database connection. Applications that do string escaping
"by hand" should be modified to rely on library routines instead.
* Fix some incorrect encoding conversion functions win1251_to_iso,
alt_to_iso, euc_tw_to_big5, euc_tw_to_mic, mic_to_euc_tw were all
broken to varying extents.
* Clean up stray remaining uses of \' in strings (Bruce, Jan)
* Fix server to use custom DH SSL parameters correctly (Michael Fuhr)
* Fix various minor memory leaks
Additionally for 7.4.13 and later:
* Fix bug that sometimes caused OR'd index scans to miss rows they
should have returned
* Fix WAL replay for case where a btree index has been truncated
* Fix SIMILAR TO for patterns involving | (Tom)
* Fix for Bonjour on Intel Macs (Ashley Clark)
Additionally for 8.0.8 and 8.1.4:
* Fix SELECT INTO and CREATE TABLE AS to create tables in the
default tablespace, not the base directory (Kris Jurka)
* Fix problem with password prompting on some Win32 systems (Robert
Kinberg)
Additionally for 8.1.4:
* Fix weak key selection in pgcrypto (Marko Kreen)
Errors in fortuna PRNG reseeding logic could cause a predictable
session key to be selected by pgp_sym_encrypt() in some cases.
This only affects non-OpenSSL-using builds.
* Make autovacuum visible in pg_stat_activity (Alvaro)
* Disable full_page_writes (Tom)
In certain cases, having full_page_writes off would cause crash
recovery to fail. A proper fix will appear in 8.2; for now it's
just disabled.
* Various planner fixes, particularly for bitmap index scans and
MIN/MAX optimization (Tom)
* Fix incorrect optimization in merge join (Tom)
Outer joins could sometimes emit multiple copies of unmatched
rows.
* Fix crash from using and modifying a plpgsql function in the same
transaction
* Improve qsort performance (Dann Corbit)
Currently this code is only used on Solaris.
* Improve pg_dump's handling of default values for domains
* Fix pg_dumpall to handle identically-named users and groups
reasonably (only possible when dumping from a pre-8.1 server) (Tom)
The user and group will be merged into a single role with LOGIN
permission. Formerly the merged role wouldn't have LOGIN
permission, making it unusable as a user.
* Fix pg_restore -n to work as documented (Tom)
Update PostgreSQL to 7.3.15, 7.4.13, 8.0.8 and 8.1.4 respectively.
Common to all versions:
* Change the server to reject invalidly-encoded multibyte characters
in all cases (Tatsuo, Tom) While PostgreSQL has been moving in this
direction for some time, the checks are now applied uniformly to
all encodings and all textual input, and are now always errors not
merely warnings. This change defends against SQL-injection attacks
of the type described in CVE-2006-2313.
* Reject unsafe uses of \' in string literals As a server-side
defense against SQL-injection attacks of the type described in
CVE-2006-2314, the server now only accepts '' and not \' as a
representation of ASCII single quote in SQL string literals. By
default, \' is rejected only when client_encoding is set to a
client-only encoding (SJIS, BIG5, GBK, GB18030, or UHC), which is
the scenario in which SQL injection is possible. A new
configuration parameter backslash_quote is available to adjust
this behavior when needed. Note that full security against
CVE-2006-2314 may require client-side changes; the purpose of
backslash_quote is in part to make it obvious that insecure clients
are insecure.
* Modify libpq's string-escaping routines to be aware of encoding
considerations This fixes libpq-using applications for the
security issues described in CVE-2006-2313 and CVE-2006-2314.
Applications that use multiple PostgreSQL connections concurrently
should migrate to PQescapeStringConn() and PQescapeByteaConn() to
ensure that escaping is done correctly for the settings in use in
each database connection. Applications that do string escaping
"by hand" should be modified to rely on library routines instead.
* Fix some incorrect encoding conversion functions win1251_to_iso,
alt_to_iso, euc_tw_to_big5, euc_tw_to_mic, mic_to_euc_tw were all
broken to varying extents.
* Clean up stray remaining uses of \' in strings (Bruce, Jan)
* Fix server to use custom DH SSL parameters correctly (Michael Fuhr)
* Fix various minor memory leaks
Additionally for 7.4.13 and later:
* Fix bug that sometimes caused OR'd index scans to miss rows they
should have returned
* Fix WAL replay for case where a btree index has been truncated
* Fix SIMILAR TO for patterns involving | (Tom)
* Fix for Bonjour on Intel Macs (Ashley Clark)
Additionally for 8.0.8 and 8.1.4:
* Fix SELECT INTO and CREATE TABLE AS to create tables in the
default tablespace, not the base directory (Kris Jurka)
* Fix problem with password prompting on some Win32 systems (Robert
Kinberg)
Additionally for 8.1.4:
* Fix weak key selection in pgcrypto (Marko Kreen)
Errors in fortuna PRNG reseeding logic could cause a predictable
session key to be selected by pgp_sym_encrypt() in some cases.
This only affects non-OpenSSL-using builds.
* Make autovacuum visible in pg_stat_activity (Alvaro)
* Disable full_page_writes (Tom)
In certain cases, having full_page_writes off would cause crash
recovery to fail. A proper fix will appear in 8.2; for now it's
just disabled.
* Various planner fixes, particularly for bitmap index scans and
MIN/MAX optimization (Tom)
* Fix incorrect optimization in merge join (Tom)
Outer joins could sometimes emit multiple copies of unmatched
rows.
* Fix crash from using and modifying a plpgsql function in the same
transaction
* Improve qsort performance (Dann Corbit)
Currently this code is only used on Solaris.
* Improve pg_dump's handling of default values for domains
* Fix pg_dumpall to handle identically-named users and groups
reasonably (only possible when dumping from a pre-8.1 server) (Tom)
The user and group will be merged into a single role with LOGIN
permission. Formerly the merged role wouldn't have LOGIN
permission, making it unusable as a user.
* Fix pg_restore -n to work as documented (Tom)
use MASTER_SITE_PGSQL
Over 1200 files touched but no revisions bumped :) 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).
Pullup ticket 1164 - requested by Joerg Sonnenberger
mostly sync databases/postgresql73{,-client,-docs,-lib,-plperl,-pltcl,-server}, databases/{tcl,tk}-postgresql73 with HEAD, via patch, including security fix.
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
Update PostgreSQL to 7.3.14. It might be needed to REINDEX indexes or textual coloumns for the issues about plperl and locales in the 7.3.13 changes are present. See the release documentation for further details. Changes from 7.3.10 to 7.3.11: - 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 missing rows in queries like UPDATE a=... WHERE a... with GiST index on column a - Improve checking for partially-written WAL pages - Improve robustness of signal handling when SSL is enabled - Various memory leakage fixes - Various portability improvements - Fix PL/PgSQL to handle var := var correctly when the variable is of pass-by-reference type Changes from 7.3.11 to 7.3.12: - Fix race condition in transaction log management - /contrib/ltree fixes (Teodor) - Fix longstanding planning error for outer joins - Prevent core dump in pg_autovacuum when a table has been dropped Changes from 7.3.12 to 7.3.13: - 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.3.13 to 7.3.14: - 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) - 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)
conflict with postgres81
Ran "pkglint --autofix", which corrected some of the quoting issues in CONFIGURE_ARGS.
Allow build on DragonFly.
Pullup ticket 684 - requested by Adrian Portelli
security update for postgresql73
Revisions pulled up:
- pkgsrc/databases/postgresql73/Makefile.common 1.10, 1.11
- pkgsrc/databases/postgresql73/distinfo 1.10
- pkgsrc/databases/postgresql73/patches/patch-al removed
- pkgsrc/databases/postgresql73-docs/PLIST 1.5
- pkgsrc/databases/postgresql73-lib/Makefile 1.11, 1.12
- pkgsrc/databases/postgresql73-lib/buildlink3.mk 1.3
Module Name: pkgsrc
Committed By: jschauma
Date: Wed Jul 13 15:34:01 UTC 2005
Modified Files:
pkgsrc/databases/postgresql73: Makefile.common
Log Message:
add template for IRIX
---
Module Name: pkgsrc
Committed By: jlam
Date: Fri Jul 15 18:27:56 UTC 2005
Modified Files:
pkgsrc/databases/postgresql73-lib: Makefile
pkgsrc/databases/postgresql73-server: Makefile
Log Message:
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making
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.
---
Module Name: pkgsrc
Committed By: adrianp
Date: Sun Aug 7 18:19:16 UTC 2005
Modified Files:
pkgsrc/databases/postgresql73: Makefile.common distinfo
pkgsrc/databases/postgresql73-docs: PLIST
pkgsrc/databases/postgresql73-lib: Makefile buildlink3.mk
pkgsrc/databases/postgresql73-plperl: Makefile
Removed Files:
pkgsrc/databases/postgresql73/patches: patch-al
Log Message:
Update to 7.3.10
Posted on 2005-05-12:
In order to address several security issues identified over the past two
weeks, as well as one "low probability" race condition, we are releasing
new version of PostgreSQL as far back as the 7.2.x branch.
Please note that the security issues were those already reported by Tom
Lane, as well as a manual fix for them. These releases are mainly to
ensure that those installing and/or upgrading existing installations have
those fixes automatically.
For details on the fixes, please see the HISTORY file included in
the Release, but a summary consists of:
* Change encoding function signature to prevent misuse
* Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function
results
* Repair race condition between relation extension and VACUUM This could
theoretically have caused loss of a page's worth of freshly-inserted
data, although the scenario seems of very low probability. There are
no known cases of it having caused more than an Assert failure.
Update to 7.3.10 Posted on 2005-05-12: In order to address several security issues identified over the past two weeks, as well as one "low probability" race condition, we are releasing new version of PostgreSQL as far back as the 7.2.x branch. Please note that the security issues were those already reported by Tom Lane, as well as a manual fix for them. These releases are mainly to ensure that those installing and/or upgrading existing installations have those fixes automatically. For details on the fixes, please see the HISTORY file included in the Release, but a summary consists of: * Change encoding function signature to prevent misuse * Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function results * Repair race condition between relation extension and VACUUM This could theoretically have caused loss of a page's worth of freshly-inserted data, although the scenario seems of very low probability. There are no known cases of it having caused more than an Assert failure.
add template for IRIX
Remove mk/autoconf.mk and mk/automake.mk and replace their usage with
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or
"automake14". Also, we don't need to call the auto* tools via
${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care
to symlink the correct tool to the correct name, so we can just use
aclocal, autoconf, etc.
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
conflicts also with pg80
Update to postgresql 7.3.9. This release contains a variety of fixes
from 7.3.8, including several security-related issues. A dump/restore
is not required for those running 7.3.X.
Changes
* Disallow "LOAD" to non-superusers
On platforms that will automatically execute initialization
functions of a shared library (this includes at least Windows and
ELF-based Unixen), "LOAD" can be used to make the server execute
arbitrary code. Thanks to NGS Software for reporting this.
* Check that creator of an aggregate function has the right to
execute the specified transition functions
This oversight made it possible to bypass denial of EXECUTE
permission on a function.
* Fix security and 64-bit issues in contrib/intagg
* Add needed STRICT marking to some contrib functions (Kris Jurka)
* Avoid buffer overrun when plpgsql cursor declaration has too many
parameters (Neil)
* Fix planning error for FULL and RIGHT outer joins
The result of the join was mistakenly supposed to be sorted the
same as the left input. This could not only deliver mis-sorted
output to the user, but in case of nested merge joins could give
outright wrong answers.
* Fix plperl for quote marks in tuple fields
* Fix display of negative intervals in SQL and GERMAN datestyles
Pullup ticket 126 - requested by Havard Eidnes
security and bug fixes for postgresql73
Module Name: pkgsrc
Committed By: jdolecek
Date: Sun Oct 10 15:58:03 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73-client: Makefile
Log Message:
kill -O pax argument - it's not portable, and it's not needed here
in first place
fixes PR pkg/23829 by Michal Pasternak
---
Module Name: pkgsrc
Committed By: jdolecek
Date: Sun Oct 10 17:27:43 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73: Makefile.common
Added Files:
pkgsrc/databases/postgresql73/files: netbsd.c netbsd.h
Log Message:
Update the NetBSD dynloader wrapper code to use straigh dl*() calls on all
archs. This fixes support for dynamic loading on mips and also improves
error reporting.
Fixes PR pkg/25473 by Byron Servies.
PKGREVISION not bumped, will ride update to 7.3.7
---
Module Name: pkgsrc
Committed By: jdolecek
Date: Sun Oct 10 17:46:07 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73: Makefile.common distinfo
pkgsrc/databases/postgresql73-client: Makefile
pkgsrc/databases/postgresql73-lib: Makefile
pkgsrc/databases/postgresql73-pltcl: Makefile
pkgsrc/databases/postgresql73-server: Makefile
pkgsrc/doc: CHANGES
Log Message:
Update to PostgreSQL 7.3.7.
Changes:
* 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.
* Remove asymmetrical word processing in tsearch (Teodor)
* Properly schema-qualify function names when pg_dump'ing a CAST
---
Module Name: pkgsrc
Committed By: jdolecek
Date: Sun Oct 10 17:48:34 UTC 2004
Modified Files:
pkgsrc/databases/jdbc-postgresql: Makefile distinfo
pkgsrc/doc: CHANGES
Log Message:
Update to JDBC driver included with PostgreSQL 7.3.7.
Notable change in 7.3.5:
* Remove ability to bind a list of values to a single parameter in
JDBC (prevents possible SQL-injection attacks)
---
Module Name: pkgsrc
Committed By: kristerw
Date: Thu Oct 14 17:58:43 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73-docs: Makefile PLIST
Log Message:
Correct PLIST.
Bump PKGREVISION.
---
Module Name: pkgsrc
Committed By: jdolecek
Date: Sun Oct 10 18:26:00 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73: distinfo
pkgsrc/databases/postgresql73/patches: patch-ad
Added Files:
pkgsrc/databases/postgresql73/patches: patch-aj
Log Message:
add patches to make it possible to compile PL/Python
---
Module Name: pkgsrc
Committed By: jdolecek
Date: Mon Oct 25 17:40:01 UTC 2004
Modified Files:
pkgsrc/databases/jdbc-postgresql: Makefile distinfo
pkgsrc/databases/postgresql73: Makefile.common distinfo
pkgsrc/databases/postgresql73-docs: Makefile
pkgsrc/doc: CHANGES
Log Message:
Update all postgresql73 packages to 7.3.8. This fixes following two issues:
* 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.
---
Module Name: pkgsrc
Committed By: he
Date: Mon Nov 1 22:32:26 UTC 2004
Modified Files:
pkgsrc/databases/postgresql73-docs: PLIST
Log Message:
Correct PLIST after upgrade to postgresql 7.3.8.
Update all postgresql73 packages to 7.3.8. This fixes following two issues: * 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.
Update to PostgreSQL 7.3.7.
Changes:
* 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.
* Remove asymmetrical word processing in tsearch (Teodor)
* Properly schema-qualify function names when pg_dump'ing a CAST
Update the NetBSD dynloader wrapper code to use straigh dl*() calls on all archs. This fixes support for dynamic loading on mips and also improves error reporting. Fixes PR pkg/25473 by Byron Servies. PKGREVISION not bumped, will ride update to 7.3.7
For once it seems that the right package wildcard for CONFLICT is '-*' instead of '-[0-9]*'. Otherwise postsgreql74-lib-whatever can be incorrectly installed alongside postgresql73-lib-whatever because the latter does not match 'postgresql73-[0-9]*'.
reimport of postgresql as postgresql73 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.
Initial revision