summaryrefslogtreecommitdiff
path: root/databases/postgresql83-server
diff options
context:
space:
mode:
authoradam <adam@pkgsrc.org>2008-06-20 06:54:42 +0000
committeradam <adam@pkgsrc.org>2008-06-20 06:54:42 +0000
commit5fe9be435e8716654ed55e736bfbcc7d76e88346 (patch)
treefcf62849edff148ce8645cbe6484211df72062b4 /databases/postgresql83-server
parentab2757eb085c24d88d987c8fb654328d518f48f1 (diff)
downloadpkgsrc-5fe9be435e8716654ed55e736bfbcc7d76e88346.tar.gz
Changes 8.3.3:
* Make pg_get_ruledef() parenthesize negative constants (Tom) Before this fix, a negative constant in a view or rule might be dumped as, say, -42::integer, which is subtly incorrect: it should be (-42)::integer due to operator precedence rules. Usually this would make little difference, but it could interact with another recent patch to cause PostgreSQL to reject what had been a valid "SELECT DISTINCT" view query. Since this could result in pg_dump output failing to reload, it is being treated as a high-priority fix. The only released versions in which dump output is actually incorrect are 8.3.1 and 8.2.7. * Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom) This oversight could lead to problems if the aggregate was later involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
Diffstat (limited to 'databases/postgresql83-server')
-rw-r--r--databases/postgresql83-server/PLIST5
1 files changed, 4 insertions, 1 deletions
diff --git a/databases/postgresql83-server/PLIST b/databases/postgresql83-server/PLIST
index d2316d15683..6c503c9ef68 100644
--- a/databases/postgresql83-server/PLIST
+++ b/databases/postgresql83-server/PLIST
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.2 2008/04/05 16:39:27 adam Exp $
+@comment $NetBSD: PLIST,v 1.3 2008/06/20 06:54:42 adam Exp $
${PG_SUBPREFIX}bin/postgres
${PG_SUBPREFIX}bin/postmaster
${PG_SUBPREFIX}lib/postgresql/ascii_and_mic.la
@@ -130,6 +130,7 @@ ${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/La_Rioja
${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/Mendoza
${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/Rio_Gallegos
${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/San_Juan
+${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/San_Luis
${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/Tucuman
${PG_SUBPREFIX}share/postgresql/timezone/America/Argentina/Ushuaia
${PG_SUBPREFIX}share/postgresql/timezone/America/Aruba
@@ -306,6 +307,7 @@ ${PG_SUBPREFIX}share/postgresql/timezone/Asia/Dubai
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Dushanbe
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Gaza
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Harbin
+${PG_SUBPREFIX}share/postgresql/timezone/Asia/Ho_Chi_Minh
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Hong_Kong
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Hovd
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Irkutsk
@@ -318,6 +320,7 @@ ${PG_SUBPREFIX}share/postgresql/timezone/Asia/Kamchatka
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Karachi
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Kashgar
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Katmandu
+${PG_SUBPREFIX}share/postgresql/timezone/Asia/Kolkata
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Krasnoyarsk
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Kuala_Lumpur
${PG_SUBPREFIX}share/postgresql/timezone/Asia/Kuching