kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/databases/postgresql81-server/pkg-plist-server

746 lines
31 KiB
Text
Raw Normal View History

Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
bin/ipcclean
bin/initdb
bin/pg_controldata
bin/pg_ctl
bin/pg_resetxlog
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
bin/postgres
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
bin/postmaster
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
etc/periodic/daily/502.pgsql
Fixing problems with the recent security patch: When bison was not installed, the patched gram.y file would not be used and the security patch would be a no-op. Also, I've had reports of compilation errors related to bison. Since checking for the correct version of bison is hard and error prone, I'm doing what the postgresql distribution does - patching the yacc:ed .c file to get rid of the building dependency. Bumping portrevision of -server. Pointy hat to: me Noticed by: Mike Harding and others Security: http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html Approved by: seanc (implicit)
2005-05-11 02:40:15 +02:00
lib/libpgport.a
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
lib/postgresql/ascii_and_mic.so
lib/postgresql/cyrillic_and_mic.so
lib/postgresql/euc_cn_and_mic.so
lib/postgresql/euc_jp_and_sjis.so
lib/postgresql/euc_kr_and_mic.so
lib/postgresql/euc_tw_and_big5.so
lib/postgresql/latin2_and_win1250.so
lib/postgresql/latin_and_mic.so
lib/postgresql/utf8_and_ascii.so
lib/postgresql/utf8_and_big5.so
lib/postgresql/utf8_and_cyrillic.so
lib/postgresql/utf8_and_euc_cn.so
lib/postgresql/utf8_and_euc_jp.so
lib/postgresql/utf8_and_euc_kr.so
lib/postgresql/utf8_and_euc_tw.so
lib/postgresql/utf8_and_gb18030.so
lib/postgresql/utf8_and_gbk.so
lib/postgresql/utf8_and_iso8859.so
lib/postgresql/utf8_and_iso8859_1.so
lib/postgresql/utf8_and_johab.so
lib/postgresql/utf8_and_sjis.so
lib/postgresql/utf8_and_uhc.so
lib/postgresql/utf8_and_win1250.so
Welcome to PostgreSQL 8.1. The new release includes performance improvements and advanced SQL features which will support bigger data warehouses, higher-volume transaction processing, and more complex distributed enterprise software. Major new features in this release include: Roles: PostgreSQL now supports database roles, which simplify the management of large numbers of users with complex overlapping database rights. IN/OUT Parameters: PostgreSQL functions now support IN, OUT and INOUT parameters, which substantially improves support of complex business logic for J2EE and .NET applications. Two-Phase Commit (2PC): Long in demand for WAN applications and heterogeneous data centers using PostgreSQL, this feature allows ACID-compliant transactions across widely separated servers. Some Performance Enhancements found in this release include: Improved Multiprocessor (SMP) Performance: The buffer manager for 8.1 has been enhanced to scale almost linearly with the number of processors, leading to significant performance gains on 8-way, 16-way, dual-core, and multi-core CPU servers. Bitmap Scan: Indexes will be dynamically converted to bitmaps in memory when appropriate, giving up to twenty times faster index performance on complex queries against very large tables. Table Partitioning: The query planner is now able to avoid scanning whole sections of a large table using a technique known as Constraint Exclusion. Shared Row Locking: PostgreSQL's "better than row-level locking" now supports even higher levels of concurrency through the addition of shared row locks for foreign keys. For a more complete listing of changes in this release, please see the Release Notes visible at: http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
lib/postgresql/utf8_and_win1252.so
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
lib/postgresql/utf8_and_win1256.so
Welcome to PostgreSQL 8.1. The new release includes performance improvements and advanced SQL features which will support bigger data warehouses, higher-volume transaction processing, and more complex distributed enterprise software. Major new features in this release include: Roles: PostgreSQL now supports database roles, which simplify the management of large numbers of users with complex overlapping database rights. IN/OUT Parameters: PostgreSQL functions now support IN, OUT and INOUT parameters, which substantially improves support of complex business logic for J2EE and .NET applications. Two-Phase Commit (2PC): Long in demand for WAN applications and heterogeneous data centers using PostgreSQL, this feature allows ACID-compliant transactions across widely separated servers. Some Performance Enhancements found in this release include: Improved Multiprocessor (SMP) Performance: The buffer manager for 8.1 has been enhanced to scale almost linearly with the number of processors, leading to significant performance gains on 8-way, 16-way, dual-core, and multi-core CPU servers. Bitmap Scan: Indexes will be dynamically converted to bitmaps in memory when appropriate, giving up to twenty times faster index performance on complex queries against very large tables. Table Partitioning: The query planner is now able to avoid scanning whole sections of a large table using a technique known as Constraint Exclusion. Shared Row Locking: PostgreSQL's "better than row-level locking" now supports even higher levels of concurrency through the addition of shared row locks for foreign keys. For a more complete listing of changes in this release, please see the Release Notes visible at: http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
lib/postgresql/utf8_and_win1258.so
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
lib/postgresql/utf8_and_win874.so
lib/postgresql/plpgsql.so
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
%%DOCSDIR%%/README-server
eplace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtry Approved by: krion@ PR: ports/88711 (related)
2006-01-22 06:52:28 +01:00
@dirrmtry %%DOCSDIR%%
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
share/postgresql/conversion_create.sql
share/postgresql/information_schema.sql
share/postgresql/pg_hba.conf.sample
share/postgresql/pg_ident.conf.sample
share/postgresql/postgres.bki
share/postgresql/postgres.description
share/postgresql/postgresql.conf.sample
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/recovery.conf.sample
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
share/postgresql/sql_features.txt
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/system_views.sql
%%GETTEXT%%share/locale/af/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/cs/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/cs/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/cs/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/cs/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/cs/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/de/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/de/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/de/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/de/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/de/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/es/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/es/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/es/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/es/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/es/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/fa/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/fr/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/fr/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/fr/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/fr/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/fr/LC_MESSAGES/postgres.mo
%%GETTEXT%%share/locale/hr/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/hu/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/hu/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/hu/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/it/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/it/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/it/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/it/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/ko/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/ko/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/ko/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/ko/LC_MESSAGES/pg_resetxlog.mo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
%%GETTEXT%%share/locale/ko/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/nb/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/nb/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/nb/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/pl/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/pl/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/pt_BR/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/pt_BR/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/pt_BR/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/pt_BR/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/pt_BR/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/ro/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/ro/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/ro/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/ro/LC_MESSAGES/pg_resetxlog.mo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
%%GETTEXT%%share/locale/ro/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/ru/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/ru/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/ru/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/ru/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/ru/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/sk/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/sk/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/sk/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/sk/LC_MESSAGES/pg_resetxlog.mo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
%%GETTEXT%%share/locale/sk/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/sl/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/sl/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/sl/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/sl/LC_MESSAGES/pg_resetxlog.mo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
%%GETTEXT%%share/locale/sl/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/sv/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/sv/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/sv/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/sv/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/sv/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/tr/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/tr/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/tr/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/tr/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/tr/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/zh_CN/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/zh_CN/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/zh_CN/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/zh_CN/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/zh_CN/LC_MESSAGES/postgres.mo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
%%GETTEXT%%share/locale/zh_TW/LC_MESSAGES/initdb.mo
%%GETTEXT%%share/locale/zh_TW/LC_MESSAGES/pg_controldata.mo
%%GETTEXT%%share/locale/zh_TW/LC_MESSAGES/pg_ctl.mo
%%GETTEXT%%share/locale/zh_TW/LC_MESSAGES/pg_resetxlog.mo
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
%%GETTEXT%%share/locale/zh_TW/LC_MESSAGES/postgres.mo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Abidjan
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Accra
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Addis_Ababa
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Algiers
Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively: The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 18:10:54 +02:00
share/postgresql/timezone/Africa/Asmara
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Asmera
share/postgresql/timezone/Africa/Bamako
share/postgresql/timezone/Africa/Bangui
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Banjul
share/postgresql/timezone/Africa/Bissau
share/postgresql/timezone/Africa/Blantyre
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Brazzaville
share/postgresql/timezone/Africa/Bujumbura
share/postgresql/timezone/Africa/Cairo
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Casablanca
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Ceuta
share/postgresql/timezone/Africa/Conakry
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Dakar
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Dar_es_Salaam
share/postgresql/timezone/Africa/Djibouti
share/postgresql/timezone/Africa/Douala
share/postgresql/timezone/Africa/El_Aaiun
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Freetown
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Gaborone
share/postgresql/timezone/Africa/Harare
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Johannesburg
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Kampala
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Khartoum
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Kigali
share/postgresql/timezone/Africa/Kinshasa
share/postgresql/timezone/Africa/Lagos
share/postgresql/timezone/Africa/Libreville
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Lome
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Luanda
share/postgresql/timezone/Africa/Lubumbashi
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Africa/Lusaka
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Africa/Malabo
share/postgresql/timezone/Africa/Maputo
share/postgresql/timezone/Africa/Maseru
share/postgresql/timezone/Africa/Mbabane
share/postgresql/timezone/Africa/Mogadishu
share/postgresql/timezone/Africa/Monrovia
share/postgresql/timezone/Africa/Nairobi
share/postgresql/timezone/Africa/Ndjamena
share/postgresql/timezone/Africa/Niamey
share/postgresql/timezone/Africa/Nouakchott
share/postgresql/timezone/Africa/Ouagadougou
share/postgresql/timezone/Africa/Porto-Novo
share/postgresql/timezone/Africa/Sao_Tome
share/postgresql/timezone/Africa/Timbuktu
share/postgresql/timezone/Africa/Tripoli
share/postgresql/timezone/Africa/Tunis
share/postgresql/timezone/Africa/Windhoek
share/postgresql/timezone/America/Adak
share/postgresql/timezone/America/Anchorage
share/postgresql/timezone/America/Anguilla
share/postgresql/timezone/America/Antigua
share/postgresql/timezone/America/Araguaina
share/postgresql/timezone/America/Argentina/Buenos_Aires
share/postgresql/timezone/America/Argentina/Catamarca
share/postgresql/timezone/America/Argentina/ComodRivadavia
share/postgresql/timezone/America/Argentina/Cordoba
share/postgresql/timezone/America/Argentina/Jujuy
share/postgresql/timezone/America/Argentina/La_Rioja
share/postgresql/timezone/America/Argentina/Mendoza
share/postgresql/timezone/America/Argentina/Rio_Gallegos
Update PostgreSQL to latest version , 8.1.15
2008-11-07 20:29:56 +01:00
share/postgresql/timezone/America/Argentina/Salta
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Argentina/San_Juan
Updates of the PostgreSQL ports Updates for all maintained versions of PostgreSQL are available today: 8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21. These releases fix more than two dozen minor issues reported and patched over the last few months. All PostgreSQL users should plan to update at their earliest convenience. People in affected time zones, in particular, should upgrade as soon as possible. Release Notes: http://www.postgresql.org/docs/8.3/static/release.html Also, fix umask error in periodic script [1]. PR: ports/124457 [1] Submitted by: Alexandre Perrin
2008-06-13 01:46:07 +02:00
share/postgresql/timezone/America/Argentina/San_Luis
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Argentina/Tucuman
share/postgresql/timezone/America/Argentina/Ushuaia
share/postgresql/timezone/America/Aruba
share/postgresql/timezone/America/Asuncion
share/postgresql/timezone/America/Atikokan
share/postgresql/timezone/America/Atka
share/postgresql/timezone/America/Bahia
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/America/Bahia_Banderas
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Barbados
share/postgresql/timezone/America/Belem
share/postgresql/timezone/America/Belize
share/postgresql/timezone/America/Blanc-Sablon
share/postgresql/timezone/America/Boa_Vista
share/postgresql/timezone/America/Bogota
share/postgresql/timezone/America/Boise
share/postgresql/timezone/America/Buenos_Aires
share/postgresql/timezone/America/Cambridge_Bay
share/postgresql/timezone/America/Campo_Grande
share/postgresql/timezone/America/Cancun
share/postgresql/timezone/America/Caracas
share/postgresql/timezone/America/Catamarca
share/postgresql/timezone/America/Cayenne
share/postgresql/timezone/America/Cayman
share/postgresql/timezone/America/Chicago
share/postgresql/timezone/America/Chihuahua
share/postgresql/timezone/America/Coral_Harbour
share/postgresql/timezone/America/Cordoba
share/postgresql/timezone/America/Costa_Rica
share/postgresql/timezone/America/Cuiaba
share/postgresql/timezone/America/Curacao
share/postgresql/timezone/America/Danmarkshavn
share/postgresql/timezone/America/Dawson
share/postgresql/timezone/America/Dawson_Creek
share/postgresql/timezone/America/Denver
share/postgresql/timezone/America/Detroit
share/postgresql/timezone/America/Dominica
share/postgresql/timezone/America/Edmonton
share/postgresql/timezone/America/Eirunepe
share/postgresql/timezone/America/El_Salvador
share/postgresql/timezone/America/Ensenada
share/postgresql/timezone/America/Fort_Wayne
share/postgresql/timezone/America/Fortaleza
share/postgresql/timezone/America/Glace_Bay
share/postgresql/timezone/America/Godthab
share/postgresql/timezone/America/Goose_Bay
share/postgresql/timezone/America/Grand_Turk
share/postgresql/timezone/America/Grenada
share/postgresql/timezone/America/Guadeloupe
share/postgresql/timezone/America/Guatemala
share/postgresql/timezone/America/Guayaquil
share/postgresql/timezone/America/Guyana
share/postgresql/timezone/America/Halifax
share/postgresql/timezone/America/Havana
share/postgresql/timezone/America/Hermosillo
share/postgresql/timezone/America/Indiana/Indianapolis
share/postgresql/timezone/America/Indiana/Knox
share/postgresql/timezone/America/Indiana/Marengo
share/postgresql/timezone/America/Indiana/Petersburg
Update PostgreSQL ports to the latest patch releases. PR: ports/104075
2007-09-17 18:45:00 +02:00
share/postgresql/timezone/America/Indiana/Tell_City
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Indiana/Vevay
share/postgresql/timezone/America/Indiana/Vincennes
Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively: The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 18:10:54 +02:00
share/postgresql/timezone/America/Indiana/Winamac
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Indianapolis
share/postgresql/timezone/America/Inuvik
share/postgresql/timezone/America/Iqaluit
share/postgresql/timezone/America/Jamaica
share/postgresql/timezone/America/Jujuy
share/postgresql/timezone/America/Juneau
share/postgresql/timezone/America/Kentucky/Louisville
share/postgresql/timezone/America/Kentucky/Monticello
share/postgresql/timezone/America/Knox_IN
share/postgresql/timezone/America/La_Paz
share/postgresql/timezone/America/Lima
share/postgresql/timezone/America/Los_Angeles
share/postgresql/timezone/America/Louisville
share/postgresql/timezone/America/Maceio
share/postgresql/timezone/America/Managua
share/postgresql/timezone/America/Manaus
Update all PostgreSQL ports to latest versions. This includes a bunch of security fixes: CVE-2007-6067, CVE-2007-4772, CVE-2007-6601, CVE-2007-6600 and CVE-2007-4769. Security: http://www.postgresql.org/about/news.905
2008-01-07 14:51:57 +01:00
share/postgresql/timezone/America/Marigot
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Martinique
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/America/Matamoros
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Mazatlan
share/postgresql/timezone/America/Mendoza
share/postgresql/timezone/America/Menominee
share/postgresql/timezone/America/Merida
share/postgresql/timezone/America/Mexico_City
share/postgresql/timezone/America/Miquelon
share/postgresql/timezone/America/Moncton
share/postgresql/timezone/America/Monterrey
share/postgresql/timezone/America/Montevideo
share/postgresql/timezone/America/Montreal
share/postgresql/timezone/America/Montserrat
share/postgresql/timezone/America/Nassau
share/postgresql/timezone/America/New_York
share/postgresql/timezone/America/Nipigon
share/postgresql/timezone/America/Nome
share/postgresql/timezone/America/Noronha
share/postgresql/timezone/America/North_Dakota/Center
share/postgresql/timezone/America/North_Dakota/New_Salem
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/America/Ojinaga
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Panama
share/postgresql/timezone/America/Pangnirtung
share/postgresql/timezone/America/Paramaribo
share/postgresql/timezone/America/Phoenix
share/postgresql/timezone/America/Port-au-Prince
share/postgresql/timezone/America/Port_of_Spain
share/postgresql/timezone/America/Porto_Acre
share/postgresql/timezone/America/Porto_Velho
share/postgresql/timezone/America/Puerto_Rico
share/postgresql/timezone/America/Rainy_River
share/postgresql/timezone/America/Rankin_Inlet
share/postgresql/timezone/America/Recife
share/postgresql/timezone/America/Regina
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/America/Resolute
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Rio_Branco
share/postgresql/timezone/America/Rosario
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/America/Santa_Isabel
Update PostgreSQL to latest version , 8.1.15
2008-11-07 20:29:56 +01:00
share/postgresql/timezone/America/Santarem
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/Santiago
share/postgresql/timezone/America/Santo_Domingo
share/postgresql/timezone/America/Sao_Paulo
share/postgresql/timezone/America/Scoresbysund
share/postgresql/timezone/America/Shiprock
Update all PostgreSQL ports to latest versions. This includes a bunch of security fixes: CVE-2007-6067, CVE-2007-4772, CVE-2007-6601, CVE-2007-6600 and CVE-2007-4769. Security: http://www.postgresql.org/about/news.905
2008-01-07 14:51:57 +01:00
share/postgresql/timezone/America/St_Barthelemy
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/America/St_Johns
share/postgresql/timezone/America/St_Kitts
share/postgresql/timezone/America/St_Lucia
share/postgresql/timezone/America/St_Thomas
share/postgresql/timezone/America/St_Vincent
share/postgresql/timezone/America/Swift_Current
share/postgresql/timezone/America/Tegucigalpa
share/postgresql/timezone/America/Thule
share/postgresql/timezone/America/Thunder_Bay
share/postgresql/timezone/America/Tijuana
share/postgresql/timezone/America/Toronto
share/postgresql/timezone/America/Tortola
share/postgresql/timezone/America/Vancouver
share/postgresql/timezone/America/Virgin
share/postgresql/timezone/America/Whitehorse
share/postgresql/timezone/America/Winnipeg
share/postgresql/timezone/America/Yakutat
share/postgresql/timezone/America/Yellowknife
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Antarctica/Casey
share/postgresql/timezone/Antarctica/Davis
share/postgresql/timezone/Antarctica/DumontDUrville
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/Antarctica/Macquarie
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Antarctica/Mawson
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Antarctica/McMurdo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Antarctica/Palmer
share/postgresql/timezone/Antarctica/Rothera
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Antarctica/South_Pole
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Antarctica/Syowa
share/postgresql/timezone/Antarctica/Vostok
share/postgresql/timezone/Arctic/Longyearbyen
share/postgresql/timezone/Asia/Aden
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Almaty
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Amman
share/postgresql/timezone/Asia/Anadyr
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Aqtau
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Aqtobe
share/postgresql/timezone/Asia/Ashgabat
share/postgresql/timezone/Asia/Ashkhabad
share/postgresql/timezone/Asia/Baghdad
share/postgresql/timezone/Asia/Bahrain
share/postgresql/timezone/Asia/Baku
share/postgresql/timezone/Asia/Bangkok
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Beirut
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Bishkek
share/postgresql/timezone/Asia/Brunei
share/postgresql/timezone/Asia/Calcutta
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Choibalsan
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Chongqing
share/postgresql/timezone/Asia/Chungking
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Colombo
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Dacca
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Damascus
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Dhaka
share/postgresql/timezone/Asia/Dili
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Dubai
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Dushanbe
share/postgresql/timezone/Asia/Gaza
share/postgresql/timezone/Asia/Harbin
Updates of the PostgreSQL ports Updates for all maintained versions of PostgreSQL are available today: 8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21. These releases fix more than two dozen minor issues reported and patched over the last few months. All PostgreSQL users should plan to update at their earliest convenience. People in affected time zones, in particular, should upgrade as soon as possible. Release Notes: http://www.postgresql.org/docs/8.3/static/release.html Also, fix umask error in periodic script [1]. PR: ports/124457 [1] Submitted by: Alexandre Perrin
2008-06-13 01:46:07 +02:00
share/postgresql/timezone/Asia/Ho_Chi_Minh
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Hong_Kong
share/postgresql/timezone/Asia/Hovd
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Asia/Irkutsk
share/postgresql/timezone/Asia/Istanbul
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Jakarta
share/postgresql/timezone/Asia/Jayapura
share/postgresql/timezone/Asia/Jerusalem
share/postgresql/timezone/Asia/Kabul
share/postgresql/timezone/Asia/Kamchatka
share/postgresql/timezone/Asia/Karachi
share/postgresql/timezone/Asia/Kashgar
Update PostgreSQL to latest versions. URL: http://www.postgresql.org/about/news.1055 The PostgreSQL Project today released updates to all active branches of the PostgreSQL object-relational database system, including versions 8.3.6, 8.2.12, 8.1.16, 8.0.20 and 7.4.24. These updates include two serious fixes, for autovacuum crashes in version 8.1 and GiST indexing data loss in 8.3, and those two versions should be updated as soon as possible. These update releases also include patches for several low-risk security holes, as well as up to 17 other minor fixes, depending on your major version of PostgreSQL. Included as well are Daylight Savings Time changes for Nepal, Switzerland and Cuba. See the release notes for full details. The first serious issue affects users who are using version 8.1 with Autovacuum, which will fail when XID rollover is required. The second serious issue can cause data loss when CLUSTER is used with GiST indexes (such as full text indexes) on version 8.3. Both issues are fixed in these releases.
2009-02-10 12:59:15 +01:00
share/postgresql/timezone/Asia/Kathmandu
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Katmandu
Updates of the PostgreSQL ports Updates for all maintained versions of PostgreSQL are available today: 8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21. These releases fix more than two dozen minor issues reported and patched over the last few months. All PostgreSQL users should plan to update at their earliest convenience. People in affected time zones, in particular, should upgrade as soon as possible. Release Notes: http://www.postgresql.org/docs/8.3/static/release.html Also, fix umask error in periodic script [1]. PR: ports/124457 [1] Submitted by: Alexandre Perrin
2008-06-13 01:46:07 +02:00
share/postgresql/timezone/Asia/Kolkata
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Krasnoyarsk
share/postgresql/timezone/Asia/Kuala_Lumpur
share/postgresql/timezone/Asia/Kuching
share/postgresql/timezone/Asia/Kuwait
share/postgresql/timezone/Asia/Macao
share/postgresql/timezone/Asia/Macau
share/postgresql/timezone/Asia/Magadan
share/postgresql/timezone/Asia/Makassar
share/postgresql/timezone/Asia/Manila
share/postgresql/timezone/Asia/Muscat
share/postgresql/timezone/Asia/Nicosia
Update all PostgreSQL ports to latest version. Remove postgresql-contrib in favour for postgresqlNN-contrib. This way we will get packages built, which is nice. Security: CVE-2010-1169 Security: CVE-2010-1170 The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release fixes moderate-risk security issues with PL/perl and PL/tcl, as well as a data corruption issue with standby databases. Users of any of these three features should update their PostgreSQL installations immediately. The PL/perl security fix closes a security hole in PL/perl procedures which could allow privilege escalation on the host system, caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for details. A second patch prevents PL/tcl's pltcl_modules table from being subverted in order to run arbitrary Tcl scripts; see CVE-2010-1170. These issues only affect users who have enabled either of these two stored procedure languages. Also corrected is use of the command ALTER TABLE SET TABLESPACE, which previously could cause data corruption on Warm Standby database slaves. This issue affects only version 8.4. There are also 21 other bug fixes in this release, some of which apply only to version 8.4, and a few of which are specifically for Windows. While these are generally fixes for minor issues, among the changes are: * Fix for a combinational crash condition * Prevent normal users from resetting some GUCs in their own role definitions * Correctly apply constraint exclusion in UPDATE and DELETE queries * Minor fixes for WAL archiving * Update timezone data for 12 zones See the release notes for a full list of changes with details. Releasenotes at http://www.postgresql.org/docs/current/static/release.html
2010-05-20 17:43:39 +02:00
share/postgresql/timezone/Asia/Novokuznetsk
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Asia/Novosibirsk
share/postgresql/timezone/Asia/Omsk
share/postgresql/timezone/Asia/Oral
share/postgresql/timezone/Asia/Phnom_Penh
share/postgresql/timezone/Asia/Pontianak
share/postgresql/timezone/Asia/Pyongyang
share/postgresql/timezone/Asia/Qatar
share/postgresql/timezone/Asia/Qyzylorda
share/postgresql/timezone/Asia/Rangoon
share/postgresql/timezone/Asia/Riyadh
share/postgresql/timezone/Asia/Riyadh87
share/postgresql/timezone/Asia/Riyadh88
share/postgresql/timezone/Asia/Riyadh89
share/postgresql/timezone/Asia/Saigon
share/postgresql/timezone/Asia/Sakhalin
share/postgresql/timezone/Asia/Samarkand
share/postgresql/timezone/Asia/Seoul
share/postgresql/timezone/Asia/Shanghai
share/postgresql/timezone/Asia/Singapore
share/postgresql/timezone/Asia/Taipei
share/postgresql/timezone/Asia/Tashkent
share/postgresql/timezone/Asia/Tbilisi
share/postgresql/timezone/Asia/Tehran
share/postgresql/timezone/Asia/Tel_Aviv
share/postgresql/timezone/Asia/Thimbu
share/postgresql/timezone/Asia/Thimphu
share/postgresql/timezone/Asia/Tokyo
share/postgresql/timezone/Asia/Ujung_Pandang
share/postgresql/timezone/Asia/Ulaanbaatar
share/postgresql/timezone/Asia/Ulan_Bator
share/postgresql/timezone/Asia/Urumqi
share/postgresql/timezone/Asia/Vientiane
share/postgresql/timezone/Asia/Vladivostok
share/postgresql/timezone/Asia/Yakutsk
share/postgresql/timezone/Asia/Yekaterinburg
share/postgresql/timezone/Asia/Yerevan
share/postgresql/timezone/Atlantic/Azores
share/postgresql/timezone/Atlantic/Bermuda
share/postgresql/timezone/Atlantic/Canary
share/postgresql/timezone/Atlantic/Cape_Verde
share/postgresql/timezone/Atlantic/Faeroe
Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively: The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 18:10:54 +02:00
share/postgresql/timezone/Atlantic/Faroe
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Atlantic/Jan_Mayen
share/postgresql/timezone/Atlantic/Madeira
share/postgresql/timezone/Atlantic/Reykjavik
share/postgresql/timezone/Atlantic/South_Georgia
share/postgresql/timezone/Atlantic/St_Helena
share/postgresql/timezone/Atlantic/Stanley
share/postgresql/timezone/Australia/ACT
share/postgresql/timezone/Australia/Adelaide
share/postgresql/timezone/Australia/Brisbane
share/postgresql/timezone/Australia/Broken_Hill
share/postgresql/timezone/Australia/Canberra
share/postgresql/timezone/Australia/Currie
share/postgresql/timezone/Australia/Darwin
Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively: The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 18:10:54 +02:00
share/postgresql/timezone/Australia/Eucla
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Australia/Hobart
share/postgresql/timezone/Australia/LHI
share/postgresql/timezone/Australia/Lindeman
share/postgresql/timezone/Australia/Lord_Howe
share/postgresql/timezone/Australia/Melbourne
share/postgresql/timezone/Australia/NSW
share/postgresql/timezone/Australia/North
share/postgresql/timezone/Australia/Perth
share/postgresql/timezone/Australia/Queensland
share/postgresql/timezone/Australia/South
share/postgresql/timezone/Australia/Sydney
share/postgresql/timezone/Australia/Tasmania
share/postgresql/timezone/Australia/Victoria
share/postgresql/timezone/Australia/West
share/postgresql/timezone/Australia/Yancowinna
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Brazil/Acre
share/postgresql/timezone/Brazil/DeNoronha
share/postgresql/timezone/Brazil/East
share/postgresql/timezone/Brazil/West
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/CET
share/postgresql/timezone/CST6CDT
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Canada/Atlantic
share/postgresql/timezone/Canada/Central
share/postgresql/timezone/Canada/East-Saskatchewan
share/postgresql/timezone/Canada/Eastern
share/postgresql/timezone/Canada/Mountain
share/postgresql/timezone/Canada/Newfoundland
share/postgresql/timezone/Canada/Pacific
share/postgresql/timezone/Canada/Saskatchewan
share/postgresql/timezone/Canada/Yukon
share/postgresql/timezone/Chile/Continental
share/postgresql/timezone/Chile/EasterIsland
share/postgresql/timezone/Cuba
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/EET
share/postgresql/timezone/EST
share/postgresql/timezone/EST5EDT
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Egypt
share/postgresql/timezone/Eire
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Etc/GMT
share/postgresql/timezone/Etc/GMT+0
share/postgresql/timezone/Etc/GMT+1
share/postgresql/timezone/Etc/GMT+10
share/postgresql/timezone/Etc/GMT+11
share/postgresql/timezone/Etc/GMT+12
share/postgresql/timezone/Etc/GMT+2
share/postgresql/timezone/Etc/GMT+3
share/postgresql/timezone/Etc/GMT+4
share/postgresql/timezone/Etc/GMT+5
share/postgresql/timezone/Etc/GMT+6
share/postgresql/timezone/Etc/GMT+7
share/postgresql/timezone/Etc/GMT+8
share/postgresql/timezone/Etc/GMT+9
share/postgresql/timezone/Etc/GMT-0
share/postgresql/timezone/Etc/GMT-1
share/postgresql/timezone/Etc/GMT-10
share/postgresql/timezone/Etc/GMT-11
share/postgresql/timezone/Etc/GMT-12
share/postgresql/timezone/Etc/GMT-13
share/postgresql/timezone/Etc/GMT-14
share/postgresql/timezone/Etc/GMT-2
share/postgresql/timezone/Etc/GMT-3
share/postgresql/timezone/Etc/GMT-4
share/postgresql/timezone/Etc/GMT-5
share/postgresql/timezone/Etc/GMT-6
share/postgresql/timezone/Etc/GMT-7
share/postgresql/timezone/Etc/GMT-8
share/postgresql/timezone/Etc/GMT-9
share/postgresql/timezone/Etc/GMT0
share/postgresql/timezone/Etc/Greenwich
share/postgresql/timezone/Etc/UCT
share/postgresql/timezone/Etc/UTC
share/postgresql/timezone/Etc/Universal
share/postgresql/timezone/Etc/Zulu
share/postgresql/timezone/Europe/Amsterdam
share/postgresql/timezone/Europe/Andorra
share/postgresql/timezone/Europe/Athens
share/postgresql/timezone/Europe/Belfast
share/postgresql/timezone/Europe/Belgrade
share/postgresql/timezone/Europe/Berlin
share/postgresql/timezone/Europe/Bratislava
share/postgresql/timezone/Europe/Brussels
share/postgresql/timezone/Europe/Bucharest
share/postgresql/timezone/Europe/Budapest
share/postgresql/timezone/Europe/Chisinau
share/postgresql/timezone/Europe/Copenhagen
share/postgresql/timezone/Europe/Dublin
share/postgresql/timezone/Europe/Gibraltar
share/postgresql/timezone/Europe/Guernsey
share/postgresql/timezone/Europe/Helsinki
share/postgresql/timezone/Europe/Isle_of_Man
share/postgresql/timezone/Europe/Istanbul
share/postgresql/timezone/Europe/Jersey
share/postgresql/timezone/Europe/Kaliningrad
share/postgresql/timezone/Europe/Kiev
share/postgresql/timezone/Europe/Lisbon
share/postgresql/timezone/Europe/Ljubljana
share/postgresql/timezone/Europe/London
share/postgresql/timezone/Europe/Luxembourg
share/postgresql/timezone/Europe/Madrid
share/postgresql/timezone/Europe/Malta
share/postgresql/timezone/Europe/Mariehamn
share/postgresql/timezone/Europe/Minsk
share/postgresql/timezone/Europe/Monaco
share/postgresql/timezone/Europe/Moscow
share/postgresql/timezone/Europe/Nicosia
share/postgresql/timezone/Europe/Oslo
share/postgresql/timezone/Europe/Paris
share/postgresql/timezone/Europe/Podgorica
share/postgresql/timezone/Europe/Prague
share/postgresql/timezone/Europe/Riga
share/postgresql/timezone/Europe/Rome
share/postgresql/timezone/Europe/Samara
share/postgresql/timezone/Europe/San_Marino
share/postgresql/timezone/Europe/Sarajevo
share/postgresql/timezone/Europe/Simferopol
share/postgresql/timezone/Europe/Skopje
share/postgresql/timezone/Europe/Sofia
share/postgresql/timezone/Europe/Stockholm
share/postgresql/timezone/Europe/Tallinn
share/postgresql/timezone/Europe/Tirane
share/postgresql/timezone/Europe/Tiraspol
share/postgresql/timezone/Europe/Uzhgorod
share/postgresql/timezone/Europe/Vaduz
share/postgresql/timezone/Europe/Vatican
share/postgresql/timezone/Europe/Vienna
share/postgresql/timezone/Europe/Vilnius
share/postgresql/timezone/Europe/Volgograd
share/postgresql/timezone/Europe/Warsaw
share/postgresql/timezone/Europe/Zagreb
share/postgresql/timezone/Europe/Zaporozhye
share/postgresql/timezone/Europe/Zurich
share/postgresql/timezone/Factory
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/GB
share/postgresql/timezone/GB-Eire
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/GMT
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/GMT+0
share/postgresql/timezone/GMT-0
share/postgresql/timezone/GMT0
share/postgresql/timezone/Greenwich
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/HST
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Hongkong
share/postgresql/timezone/Iceland
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Indian/Antananarivo
share/postgresql/timezone/Indian/Chagos
share/postgresql/timezone/Indian/Christmas
share/postgresql/timezone/Indian/Cocos
share/postgresql/timezone/Indian/Comoro
share/postgresql/timezone/Indian/Kerguelen
share/postgresql/timezone/Indian/Mahe
share/postgresql/timezone/Indian/Maldives
share/postgresql/timezone/Indian/Mauritius
share/postgresql/timezone/Indian/Mayotte
share/postgresql/timezone/Indian/Reunion
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Iran
share/postgresql/timezone/Israel
share/postgresql/timezone/Jamaica
share/postgresql/timezone/Japan
share/postgresql/timezone/Kwajalein
share/postgresql/timezone/Libya
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/MET
share/postgresql/timezone/MST
share/postgresql/timezone/MST7MDT
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Mexico/BajaNorte
share/postgresql/timezone/Mexico/BajaSur
share/postgresql/timezone/Mexico/General
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Mideast/Riyadh87
share/postgresql/timezone/Mideast/Riyadh88
share/postgresql/timezone/Mideast/Riyadh89
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/NZ
share/postgresql/timezone/NZ-CHAT
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/Navajo
share/postgresql/timezone/PRC
share/postgresql/timezone/PST8PDT
share/postgresql/timezone/Pacific/Apia
share/postgresql/timezone/Pacific/Auckland
share/postgresql/timezone/Pacific/Chatham
share/postgresql/timezone/Pacific/Easter
share/postgresql/timezone/Pacific/Efate
share/postgresql/timezone/Pacific/Enderbury
share/postgresql/timezone/Pacific/Fakaofo
share/postgresql/timezone/Pacific/Fiji
share/postgresql/timezone/Pacific/Funafuti
share/postgresql/timezone/Pacific/Galapagos
share/postgresql/timezone/Pacific/Gambier
share/postgresql/timezone/Pacific/Guadalcanal
share/postgresql/timezone/Pacific/Guam
share/postgresql/timezone/Pacific/Honolulu
share/postgresql/timezone/Pacific/Johnston
share/postgresql/timezone/Pacific/Kiritimati
share/postgresql/timezone/Pacific/Kosrae
share/postgresql/timezone/Pacific/Kwajalein
share/postgresql/timezone/Pacific/Majuro
share/postgresql/timezone/Pacific/Marquesas
share/postgresql/timezone/Pacific/Midway
share/postgresql/timezone/Pacific/Nauru
share/postgresql/timezone/Pacific/Niue
share/postgresql/timezone/Pacific/Norfolk
share/postgresql/timezone/Pacific/Noumea
share/postgresql/timezone/Pacific/Pago_Pago
share/postgresql/timezone/Pacific/Palau
share/postgresql/timezone/Pacific/Pitcairn
share/postgresql/timezone/Pacific/Ponape
share/postgresql/timezone/Pacific/Port_Moresby
share/postgresql/timezone/Pacific/Rarotonga
share/postgresql/timezone/Pacific/Saipan
share/postgresql/timezone/Pacific/Samoa
share/postgresql/timezone/Pacific/Tahiti
share/postgresql/timezone/Pacific/Tarawa
share/postgresql/timezone/Pacific/Tongatapu
share/postgresql/timezone/Pacific/Truk
share/postgresql/timezone/Pacific/Wake
share/postgresql/timezone/Pacific/Wallis
share/postgresql/timezone/Pacific/Yap
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Poland
share/postgresql/timezone/Portugal
share/postgresql/timezone/ROC
share/postgresql/timezone/ROK
share/postgresql/timezone/Singapore
share/postgresql/timezone/Turkey
share/postgresql/timezone/UCT
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/US/Alaska
share/postgresql/timezone/US/Aleutian
share/postgresql/timezone/US/Arizona
share/postgresql/timezone/US/Central
share/postgresql/timezone/US/East-Indiana
share/postgresql/timezone/US/Eastern
share/postgresql/timezone/US/Hawaii
share/postgresql/timezone/US/Indiana-Starke
share/postgresql/timezone/US/Michigan
share/postgresql/timezone/US/Mountain
share/postgresql/timezone/US/Pacific
share/postgresql/timezone/US/Pacific-New
share/postgresql/timezone/US/Samoa
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/UTC
share/postgresql/timezone/Universal
share/postgresql/timezone/W-SU
Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server
2007-01-09 17:29:35 +01:00
share/postgresql/timezone/WET
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
share/postgresql/timezone/Zulu
Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively: The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 18:10:54 +02:00
share/postgresql/timezone/posixrules
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
@dirrm share/postgresql/timezone/Africa
@dirrm share/postgresql/timezone/America/Argentina
@dirrm share/postgresql/timezone/America/Indiana
@dirrm share/postgresql/timezone/America/Kentucky
@dirrm share/postgresql/timezone/America/North_Dakota
@dirrm share/postgresql/timezone/America
@dirrm share/postgresql/timezone/Antarctica
@dirrm share/postgresql/timezone/Arctic
@dirrm share/postgresql/timezone/Asia
@dirrm share/postgresql/timezone/Atlantic
@dirrm share/postgresql/timezone/Australia
@dirrm share/postgresql/timezone/Brazil
@dirrm share/postgresql/timezone/Canada
@dirrm share/postgresql/timezone/Chile
@dirrm share/postgresql/timezone/Etc
@dirrm share/postgresql/timezone/Europe
@dirrm share/postgresql/timezone/Indian
@dirrm share/postgresql/timezone/Mexico
@dirrm share/postgresql/timezone/Mideast
@dirrm share/postgresql/timezone/Pacific
@dirrm share/postgresql/timezone/US
@dirrm share/postgresql/timezone
Another step along the road to the postgresql new world order. Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer
2004-11-23 20:15:12 +01:00
@unexec if cmp -s ~pgsql/.profile %D/share/postgresql/dot.profile.dist; then rm -f ~pgsql/.profile; fi
@unexec if cmp -s ~pgsql/.cshrc %D/share/postgresql/dot.cshrc.dist; then rm -f ~pgsql/.cshrc; fi
@unexec [ -f ~pgsql/dot.profile.dist ] && rm ~pgsql/dot.profile.dist
@unexec [ -f ~pgsql/dot.cshrc.dist ] && rm ~pgsql/dot.cshrc.dist
share/postgresql/dot.profile.dist
share/postgresql/dot.cshrc.dist
@exec [ -f %D/share/postgresql/dot.profile.dist ] && cp %D/share/postgresql/dot.profile.dist ~pgsql/.
@exec [ -f %D/share/postgresql/dot.cshrc.dist ] && cp %D/share/postgresql/dot.cshrc.dist ~pgsql/.
@exec [ -f ~pgsql/.profile ] || (cp %D/share/postgresql/dot.profile.dist ~pgsql/.profile && chown pgsql:pgsql ~pgsql/.profile)
@exec [ -f ~pgsql/.cshrc ] || (cp %D/share/postgresql/dot.cshrc.dist ~pgsql/.cshrc && chown pgsql:pgsql ~pgsql/.cshrc)
Say hello to postgresql-8.0. Some of the highlights of the new version are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors)
2005-01-31 01:36:16 +01:00
@unexec echo "Warning: If you will *NOT* use this package anymore, please remove the pgsql user manually."
eplace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtry Approved by: krion@ PR: ports/88711 (related)
2006-01-22 06:52:28 +01:00
@dirrmtry share/postgresql
@dirrmtry etc/periodic/daily
@dirrmtry etc/periodic
@dirrmtry lib/postgresql
@dirrmtry pgsql
Reference in a new issue Copy permalink