diff options
| author | adam <adam> | 2008-06-20 07:46:49 +0000 |
|---|---|---|
| committer | adam <adam> | 2008-06-20 07:46:49 +0000 |
| commit | 6b3b78ba17a577a4e792a032e79bc867418ba263 (patch) | |
| tree | 64ef8b3e8881f77824b402a35014189a49e6dde4 /databases/postgresql82-server | |
| parent | 1b1e30917a49c39523d81893757d739badde72a9 (diff) | |
| download | pkgsrc-6b3b78ba17a577a4e792a032e79bc867418ba263.tar.gz | |
Changes 8.2.9:
* 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/postgresql82-server')
| -rw-r--r-- | databases/postgresql82-server/PLIST | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/databases/postgresql82-server/PLIST b/databases/postgresql82-server/PLIST index f95e56bfdb1..7ac8d4a6e90 100644 --- a/databases/postgresql82-server/PLIST +++ b/databases/postgresql82-server/PLIST @@ -1,4 +1,4 @@ -@comment $NetBSD: PLIST,v 1.5 2008/01/07 20:14:36 adam Exp $ +@comment $NetBSD: PLIST,v 1.6 2008/06/20 07:46:49 adam Exp $ ${PG_SUBPREFIX}bin/postgres ${PG_SUBPREFIX}bin/postmaster ${PG_SUBPREFIX}lib/postgresql/ascii_and_mic.la @@ -123,6 +123,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 @@ -299,6 +300,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 @@ -311,6 +313,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 |