kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/postgresql-docs/PLIST

618 lines
27 KiB
Text
Raw Normal View History

Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
@comment $NetBSD: PLIST,v 1.4 2003/01/05 20:12:23 jlam Exp $
share/doc/html/postgresql/admin-preface.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/admin.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/app-clusterdb.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/app-createdb.html
share/doc/html/postgresql/app-createlang.html
share/doc/html/postgresql/app-createuser.html
share/doc/html/postgresql/app-dropdb.html
share/doc/html/postgresql/app-droplang.html
share/doc/html/postgresql/app-dropuser.html
share/doc/html/postgresql/app-ecpg.html
share/doc/html/postgresql/app-initdb.html
share/doc/html/postgresql/app-initlocation.html
share/doc/html/postgresql/app-ipcclean.html
share/doc/html/postgresql/app-pg-ctl.html
share/doc/html/postgresql/app-pg-dumpall.html
share/doc/html/postgresql/app-pgconfig.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/app-pgcontroldata.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/app-pgdump.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/app-pgresetxlog.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/app-pgrestore.html
share/doc/html/postgresql/app-pgtclsh.html
share/doc/html/postgresql/app-pgtksh.html
share/doc/html/postgresql/app-postgres.html
share/doc/html/postgresql/app-postmaster.html
share/doc/html/postgresql/app-psql.html
share/doc/html/postgresql/app-vacuumdb.html
share/doc/html/postgresql/applevel-consistency.html
share/doc/html/postgresql/arch-pg.html
share/doc/html/postgresql/arrays.html
share/doc/html/postgresql/auth-methods.html
share/doc/html/postgresql/backup-file.html
share/doc/html/postgresql/backup.html
share/doc/html/postgresql/biblio.html
share/doc/html/postgresql/bki-commands.html
share/doc/html/postgresql/bki-example.html
share/doc/html/postgresql/bki.html
share/doc/html/postgresql/bug-reporting.html
share/doc/html/postgresql/catalog-pg-aggregate.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/catalog-pg-am.html
share/doc/html/postgresql/catalog-pg-amop.html
share/doc/html/postgresql/catalog-pg-amproc.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-attrdef.html
share/doc/html/postgresql/catalog-pg-attribute.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/catalog-pg-cast.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-class.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/catalog-pg-constraint.html
share/doc/html/postgresql/catalog-pg-conversion.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-database.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/catalog-pg-depend.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-description.html
share/doc/html/postgresql/catalog-pg-group.html
share/doc/html/postgresql/catalog-pg-index.html
share/doc/html/postgresql/catalog-pg-inherits.html
share/doc/html/postgresql/catalog-pg-language.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/catalog-pg-largeobject.html
share/doc/html/postgresql/catalog-pg-listener.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/catalog-pg-namespace.html
share/doc/html/postgresql/catalog-pg-opclass.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-operator.html
share/doc/html/postgresql/catalog-pg-proc.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/catalog-pg-rewrite.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-shadow.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/catalog-pg-statistic.html
share/doc/html/postgresql/catalog-pg-trigger.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/catalog-pg-type.html
share/doc/html/postgresql/catalogs.gif
share/doc/html/postgresql/catalogs.html
share/doc/html/postgresql/charset.html
share/doc/html/postgresql/client-authentication-problems.html
share/doc/html/postgresql/client-authentication.html
share/doc/html/postgresql/compiler.html
share/doc/html/postgresql/connect-estab.html
share/doc/html/postgresql/connections.gif
share/doc/html/postgresql/creating-cluster.html
share/doc/html/postgresql/cvs-tree.html
share/doc/html/postgresql/cvs.html
share/doc/html/postgresql/cvsup.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/datatype-binary.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/datatype-bit.html
share/doc/html/postgresql/datatype-boolean.html
share/doc/html/postgresql/datatype-character.html
share/doc/html/postgresql/datatype-datetime.html
share/doc/html/postgresql/datatype-geometric.html
share/doc/html/postgresql/datatype-money.html
share/doc/html/postgresql/datatype-net-types.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/datatype-oid.html
share/doc/html/postgresql/datatype-pseudo.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/datatype.html
share/doc/html/postgresql/datetime-appendix.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ddl-alter.html
share/doc/html/postgresql/ddl-constraints.html
share/doc/html/postgresql/ddl-depend.html
share/doc/html/postgresql/ddl-inherit.html
share/doc/html/postgresql/ddl-others.html
share/doc/html/postgresql/ddl-priv.html
share/doc/html/postgresql/ddl-schemas.html
share/doc/html/postgresql/ddl-system-columns.html
share/doc/html/postgresql/ddl.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/developer.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/disk-full.html
share/doc/html/postgresql/diskusage.html
share/doc/html/postgresql/dml-delete.html
share/doc/html/postgresql/dml-update.html
share/doc/html/postgresql/dml.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/doc-build.html
share/doc/html/postgresql/doc-sources.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/doc-style.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/doc-toolsets.html
share/doc/html/postgresql/docguide.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ecpg-commands.html
share/doc/html/postgresql/ecpg-connect.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/ecpg-develop.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ecpg-disconnect.html
share/doc/html/postgresql/ecpg-errors.html
share/doc/html/postgresql/ecpg-include.html
share/doc/html/postgresql/ecpg-library.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/ecpg-porting.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ecpg-process.html
share/doc/html/postgresql/ecpg-variables.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/ecpg.html
share/doc/html/postgresql/executor.html
share/doc/html/postgresql/explicit-joins.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/explicit-locking.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/extend.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/features.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/functions-aggregate.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/functions-binarystring.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/functions-comparison.html
share/doc/html/postgresql/functions-conditional.html
share/doc/html/postgresql/functions-datetime.html
share/doc/html/postgresql/functions-formatting.html
share/doc/html/postgresql/functions-geometry.html
share/doc/html/postgresql/functions-matching.html
share/doc/html/postgresql/functions-math.html
share/doc/html/postgresql/functions-misc.html
share/doc/html/postgresql/functions-net.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/functions-sequence.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/functions-string.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/functions-subquery.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/functions.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/geqo-biblio.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/geqo-intro2.html
share/doc/html/postgresql/geqo-pg-intro.html
share/doc/html/postgresql/geqo.html
share/doc/html/postgresql/gist.html
share/doc/html/postgresql/groups.html
share/doc/html/postgresql/history.html
share/doc/html/postgresql/index.html
share/doc/html/postgresql/indexcost.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/indexes-examine.html
share/doc/html/postgresql/indexes-functional.html
share/doc/html/postgresql/indexes-multicolumn.html
share/doc/html/postgresql/indexes-opclass.html
share/doc/html/postgresql/indexes-partial.html
share/doc/html/postgresql/indexes-types.html
share/doc/html/postgresql/indexes-unique.html
share/doc/html/postgresql/indexes.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/install-getsource.html
share/doc/html/postgresql/install-post.html
share/doc/html/postgresql/install-procedure.html
share/doc/html/postgresql/install-requirements.html
share/doc/html/postgresql/install-upgrading.html
share/doc/html/postgresql/install-win32.html
share/doc/html/postgresql/installation.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/jdbc-binary-data.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/jdbc-datasource.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/jdbc-ddl.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/jdbc-ext.html
share/doc/html/postgresql/jdbc-query.html
share/doc/html/postgresql/jdbc-reading.html
share/doc/html/postgresql/jdbc-thread.html
share/doc/html/postgresql/jdbc-update.html
share/doc/html/postgresql/jdbc-use.html
share/doc/html/postgresql/jdbc.html
share/doc/html/postgresql/kernel-resources.html
share/doc/html/postgresql/largeobjects.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/libpgtcl-loading.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/libpgtcl-ref.html
share/doc/html/postgresql/libpq-async.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/libpq-build.html
share/doc/html/postgresql/libpq-connect.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/libpq-control.html
share/doc/html/postgresql/libpq-copy.html
share/doc/html/postgresql/libpq-envars.html
share/doc/html/postgresql/libpq-example.html
share/doc/html/postgresql/libpq-exec.html
share/doc/html/postgresql/libpq-fastpath.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/libpq-files.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/libpq-notify.html
share/doc/html/postgresql/libpq-threading.html
share/doc/html/postgresql/libpq-trace.html
share/doc/html/postgresql/libpq.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ln17902.html
share/doc/html/postgresql/ln24595.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/ln25.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/ln37022.html
share/doc/html/postgresql/ln51737.html
share/doc/html/postgresql/ln659.html
share/doc/html/postgresql/ln8.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/lo-funcs.html
share/doc/html/postgresql/lo-implementation.html
share/doc/html/postgresql/lo-interfaces.html
share/doc/html/postgresql/lo-libpq.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/locking-indexes.html
share/doc/html/postgresql/logfile-maintenance.html
share/doc/html/postgresql/maintenance.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/manage-ag-alternate-locs.html
share/doc/html/postgresql/manage-ag-config.html
share/doc/html/postgresql/manage-ag-createdb.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/manage-ag-dropdb.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/manage-ag-templatedbs.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/managing-databases.html
share/doc/html/postgresql/migration.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/monitoring-locks.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/monitoring-stats.html
share/doc/html/postgresql/monitoring.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/multibyte.html
share/doc/html/postgresql/mvcc.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/nls-programmer.html
share/doc/html/postgresql/nls.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/notation.html
share/doc/html/postgresql/overview.html
share/doc/html/postgresql/page.html
share/doc/html/postgresql/parser-stage.html
share/doc/html/postgresql/performance-tips.html
share/doc/html/postgresql/perm-functions.html
share/doc/html/postgresql/pg-system-catalogs.html
share/doc/html/postgresql/pgtcl-pgconndefaults.html
share/doc/html/postgresql/pgtcl-pgconnect.html
share/doc/html/postgresql/pgtcl-pgdisconnect.html
share/doc/html/postgresql/pgtcl-pgexec.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/pgtcl-pgexecute.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/pgtcl-pglisten.html
share/doc/html/postgresql/pgtcl-pgloclose.html
share/doc/html/postgresql/pgtcl-pglocreat.html
share/doc/html/postgresql/pgtcl-pgloexport.html
share/doc/html/postgresql/pgtcl-pgloimport.html
share/doc/html/postgresql/pgtcl-pglolseek.html
share/doc/html/postgresql/pgtcl-pgloopen.html
share/doc/html/postgresql/pgtcl-pgloread.html
share/doc/html/postgresql/pgtcl-pglotell.html
share/doc/html/postgresql/pgtcl-pglounlink.html
share/doc/html/postgresql/pgtcl-pglowrite.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/pgtcl-pgon-connection-loss.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/pgtcl-pgresult.html
share/doc/html/postgresql/pgtcl-pgselect.html
share/doc/html/postgresql/pgtcl.html
share/doc/html/postgresql/planner-optimizer.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/planner-stats.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/plperl-data.html
share/doc/html/postgresql/plperl-database.html
share/doc/html/postgresql/plperl-missing.html
share/doc/html/postgresql/plperl-trusted.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/plperl.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/plpgsql-control-structures.html
share/doc/html/postgresql/plpgsql-cursors.html
share/doc/html/postgresql/plpgsql-declarations.html
share/doc/html/postgresql/plpgsql-errors-and-messages.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/plpgsql-examples.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/plpgsql-expressions.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/plpgsql-porting.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/plpgsql-statements.html
share/doc/html/postgresql/plpgsql-structure.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/plpgsql-trigger.html
share/doc/html/postgresql/plpgsql.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/plpython-database.html
share/doc/html/postgresql/plpython-trigger.html
share/doc/html/postgresql/plpython-trusted.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/plpython.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/pltcl-description.html
share/doc/html/postgresql/pltcl.html
share/doc/html/postgresql/populate.html
share/doc/html/postgresql/postmaster-shutdown.html
share/doc/html/postgresql/postmaster-start.html
share/doc/html/postgresql/privileges.html
share/doc/html/postgresql/programmer-client.html
share/doc/html/postgresql/programmer-pl.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/programmer-preface.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/programmer-server.html
share/doc/html/postgresql/programmer.html
share/doc/html/postgresql/protocol-message-formats.html
share/doc/html/postgresql/protocol-message-types.html
share/doc/html/postgresql/protocol-protocol.html
share/doc/html/postgresql/protocol.html
share/doc/html/postgresql/pygresql-close.html
share/doc/html/postgresql/pygresql-connect.html
share/doc/html/postgresql/pygresql-db-clear.html
share/doc/html/postgresql/pygresql-db-delete.html
share/doc/html/postgresql/pygresql-db-get-attnames.html
share/doc/html/postgresql/pygresql-db-get-databases.html
share/doc/html/postgresql/pygresql-db-get-tables.html
share/doc/html/postgresql/pygresql-db-get.html
share/doc/html/postgresql/pygresql-db-insert.html
share/doc/html/postgresql/pygresql-db-pkey.html
share/doc/html/postgresql/pygresql-db-update.html
share/doc/html/postgresql/pygresql-endcopy.html
share/doc/html/postgresql/pygresql-fileno.html
share/doc/html/postgresql/pygresql-get-defbase.html
share/doc/html/postgresql/pygresql-get-defhost.html
share/doc/html/postgresql/pygresql-get-defopt.html
share/doc/html/postgresql/pygresql-get-defport.html
share/doc/html/postgresql/pygresql-get-deftty.html
share/doc/html/postgresql/pygresql-getline.html
share/doc/html/postgresql/pygresql-getlo.html
share/doc/html/postgresql/pygresql-getnotify.html
share/doc/html/postgresql/pygresql-inserttable.html
share/doc/html/postgresql/pygresql-locreate.html
share/doc/html/postgresql/pygresql-loimport.html
share/doc/html/postgresql/pygresql-pg-db.html
share/doc/html/postgresql/pygresql-pg-functions.html
share/doc/html/postgresql/pygresql-pg-pglarge.html
share/doc/html/postgresql/pygresql-pg-pgobject.html
share/doc/html/postgresql/pygresql-pg-pgqueryobject.html
share/doc/html/postgresql/pygresql-pglargeobject-close.html
share/doc/html/postgresql/pygresql-pglargeobject-export.html
share/doc/html/postgresql/pygresql-pglargeobject-open.html
share/doc/html/postgresql/pygresql-pglargeobject-read.html
share/doc/html/postgresql/pygresql-pglargeobject-seek.html
share/doc/html/postgresql/pygresql-pglargeobject-size.html
share/doc/html/postgresql/pygresql-pglargeobject-tell.html
share/doc/html/postgresql/pygresql-pglargeobject-unlink.html
share/doc/html/postgresql/pygresql-pglargeobject-write.html
share/doc/html/postgresql/pygresql-pgqueryobject-dictresult.html
share/doc/html/postgresql/pygresql-pgqueryobject-fieldname.html
share/doc/html/postgresql/pygresql-pgqueryobject-fieldnum.html
share/doc/html/postgresql/pygresql-pgqueryobject-getresult.html
share/doc/html/postgresql/pygresql-pgqueryobject-listfields.html
share/doc/html/postgresql/pygresql-pgqueryobject-ntuples.html
share/doc/html/postgresql/pygresql-putline.html
share/doc/html/postgresql/pygresql-query.html
share/doc/html/postgresql/pygresql-reset.html
share/doc/html/postgresql/pygresql-set-defbase.html
share/doc/html/postgresql/pygresql-set-defhost.html
share/doc/html/postgresql/pygresql-set-defopt.html
share/doc/html/postgresql/pygresql-set-defport.html
share/doc/html/postgresql/pygresql-set-deftty.html
share/doc/html/postgresql/pygresql.html
share/doc/html/postgresql/queries-limit.html
share/doc/html/postgresql/queries-order.html
share/doc/html/postgresql/queries-select-lists.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/queries-table-expressions.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/queries-union.html
share/doc/html/postgresql/queries.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/querytree.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/recode.html
share/doc/html/postgresql/reference-client.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/reference-preface.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/reference-server.html
share/doc/html/postgresql/reference.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/regress-evaluation.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/regress-platform.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/regress-run.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/regress.html
share/doc/html/postgresql/release-0-01.html
share/doc/html/postgresql/release-0-02.html
share/doc/html/postgresql/release-0-03.html
share/doc/html/postgresql/release-1-0.html
share/doc/html/postgresql/release-1-01.html
share/doc/html/postgresql/release-1-02.html
share/doc/html/postgresql/release-1-09.html
share/doc/html/postgresql/release-6-0.html
share/doc/html/postgresql/release-6-1-1.html
share/doc/html/postgresql/release-6-1.html
share/doc/html/postgresql/release-6-2-1.html
share/doc/html/postgresql/release-6-2.html
share/doc/html/postgresql/release-6-3-1.html
share/doc/html/postgresql/release-6-3-2.html
share/doc/html/postgresql/release-6-3.html
share/doc/html/postgresql/release-6-4-1.html
share/doc/html/postgresql/release-6-4-2.html
share/doc/html/postgresql/release-6-4.html
share/doc/html/postgresql/release-6-5-1.html
share/doc/html/postgresql/release-6-5-2.html
share/doc/html/postgresql/release-6-5-3.html
share/doc/html/postgresql/release-6-5.html
share/doc/html/postgresql/release-7-0-1.html
share/doc/html/postgresql/release-7-0-2.html
share/doc/html/postgresql/release-7-0-3.html
share/doc/html/postgresql/release-7-0.html
Update postgresql to 7.1.2. Also update postgresql packages built from postgresql sources: postgresql-client, postgresql-docs, postgresql-lib, postgresql-server, postgresql-plperl, postgresql-pltcl, odbc-postgresql, py-postgresql, tcl-postgresql, tk-postgresql to 7.1.2 or to depend on postgresql-libs-7.1.2. Changes from version 7.1.1: Fix PL/PgSQL SELECTs when returning no rows Fix for psql backslash core dump Referential integrity permission fix Optimizer fixes pg_dump cleanups
2001-05-30 01:28:05 +02:00
share/doc/html/postgresql/release-7-1-1.html
Update postgresql and packages built from postgresql sources to 7.1.3. Relevant changes from version 7.1.2 include: Remove unused WAL segements of large transactions Multiaction rule fix Pl/pgSQL memory allocation fix VACUUM buffer fix pg_dump fixes for GRANT/REVOKE/comments on views, user-defined types Fix subselects with DISTINCT ON or LIMIT Disable COPY TO/FROM a view
2001-09-07 10:49:10 +02:00
share/doc/html/postgresql/release-7-1-2.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/release-7-1-3.html
share/doc/html/postgresql/release-7-1.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/release-7-2-1.html
share/doc/html/postgresql/release-7-2-2.html
share/doc/html/postgresql/release-7-2-3.html
Fix PLIST for postgresql 7.2.1.
2002-04-06 11:41:03 +02:00
share/doc/html/postgresql/release-7-2.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/release-7-3.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/release.html
share/doc/html/postgresql/resources.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/routine-reindex.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/routine-vacuuming.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/rule-system.html
share/doc/html/postgresql/rules-insert.html
share/doc/html/postgresql/rules-permissions.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/rules-status.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/rules-triggers.html
share/doc/html/postgresql/rules-views.html
share/doc/html/postgresql/rules.html
share/doc/html/postgresql/runtime-config.html
share/doc/html/postgresql/runtime.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/setindex.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/source.html
share/doc/html/postgresql/spi-examples.html
share/doc/html/postgresql/spi-interface-support.html
share/doc/html/postgresql/spi-memory.html
share/doc/html/postgresql/spi-spiconnect.html
share/doc/html/postgresql/spi-spicopytuple.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/spi-spicopytupledesc.html
share/doc/html/postgresql/spi-spicopytupleintoslot.html
share/doc/html/postgresql/spi-spicursor-close.html
share/doc/html/postgresql/spi-spicursor-fetch.html
share/doc/html/postgresql/spi-spicursor-find.html
share/doc/html/postgresql/spi-spicursor-move.html
share/doc/html/postgresql/spi-spicursor-open.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/spi-spiexec.html
share/doc/html/postgresql/spi-spiexecp.html
share/doc/html/postgresql/spi-spifinish.html
share/doc/html/postgresql/spi-spifname.html
share/doc/html/postgresql/spi-spifnumber.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/spi-spifreeplan.html
share/doc/html/postgresql/spi-spifreetuple.html
share/doc/html/postgresql/spi-spifreetuptable.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/spi-spigetbinval.html
share/doc/html/postgresql/spi-spigetrelname.html
share/doc/html/postgresql/spi-spigettype.html
share/doc/html/postgresql/spi-spigettypeid.html
share/doc/html/postgresql/spi-spigetvalue.html
share/doc/html/postgresql/spi-spimodifytuple.html
share/doc/html/postgresql/spi-spipalloc.html
share/doc/html/postgresql/spi-spipfree.html
share/doc/html/postgresql/spi-spiprepare.html
share/doc/html/postgresql/spi-spirepalloc.html
share/doc/html/postgresql/spi-spisaveplan.html
share/doc/html/postgresql/spi-visibility.html
share/doc/html/postgresql/spi.html
share/doc/html/postgresql/sql-abort.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-alterdatabase.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-altergroup.html
share/doc/html/postgresql/sql-altertable.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-altertrigger.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-alteruser.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/sql-analyze.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-begin.html
share/doc/html/postgresql/sql-checkpoint.html
share/doc/html/postgresql/sql-close.html
share/doc/html/postgresql/sql-cluster.html
share/doc/html/postgresql/sql-commands.html
share/doc/html/postgresql/sql-comment.html
share/doc/html/postgresql/sql-commit.html
share/doc/html/postgresql/sql-copy.html
share/doc/html/postgresql/sql-createaggregate.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-createcast.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-createconstraint.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-createconversion.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-createdatabase.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-createdomain.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-createfunction.html
share/doc/html/postgresql/sql-creategroup.html
share/doc/html/postgresql/sql-createindex.html
share/doc/html/postgresql/sql-createlanguage.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-createopclass.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-createoperator.html
share/doc/html/postgresql/sql-createrule.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-createschema.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-createsequence.html
share/doc/html/postgresql/sql-createtable.html
share/doc/html/postgresql/sql-createtableas.html
share/doc/html/postgresql/sql-createtrigger.html
share/doc/html/postgresql/sql-createtype.html
share/doc/html/postgresql/sql-createuser.html
share/doc/html/postgresql/sql-createview.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-deallocate.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-declare.html
share/doc/html/postgresql/sql-delete.html
share/doc/html/postgresql/sql-dropaggregate.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-dropcast.html
share/doc/html/postgresql/sql-dropconversion.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-dropdatabase.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-dropdomain.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-dropfunction.html
share/doc/html/postgresql/sql-dropgroup.html
share/doc/html/postgresql/sql-dropindex.html
share/doc/html/postgresql/sql-droplanguage.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-dropopclass.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-dropoperator.html
share/doc/html/postgresql/sql-droprule.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-dropschema.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-dropsequence.html
share/doc/html/postgresql/sql-droptable.html
share/doc/html/postgresql/sql-droptrigger.html
share/doc/html/postgresql/sql-droptype.html
share/doc/html/postgresql/sql-dropuser.html
share/doc/html/postgresql/sql-dropview.html
share/doc/html/postgresql/sql-end.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-execute.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-explain.html
share/doc/html/postgresql/sql-expressions.html
share/doc/html/postgresql/sql-fetch.html
share/doc/html/postgresql/sql-grant.html
share/doc/html/postgresql/sql-insert.html
share/doc/html/postgresql/sql-keywords-appendix.html
share/doc/html/postgresql/sql-listen.html
share/doc/html/postgresql/sql-load.html
share/doc/html/postgresql/sql-lock.html
share/doc/html/postgresql/sql-move.html
share/doc/html/postgresql/sql-notify.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-prepare.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-reindex.html
share/doc/html/postgresql/sql-reset.html
share/doc/html/postgresql/sql-revoke.html
share/doc/html/postgresql/sql-rollback.html
share/doc/html/postgresql/sql-select.html
share/doc/html/postgresql/sql-selectinto.html
share/doc/html/postgresql/sql-set-constraints.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/sql-set-session-authorization.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-set-transaction.html
share/doc/html/postgresql/sql-set.html
share/doc/html/postgresql/sql-show.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/sql-start-transaction.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/sql-syntax.html
share/doc/html/postgresql/sql-truncate.html
share/doc/html/postgresql/sql-unlisten.html
share/doc/html/postgresql/sql-update.html
share/doc/html/postgresql/sql-vacuum.html
share/doc/html/postgresql/ssh-tunnels.html
share/doc/html/postgresql/ssl-tcp.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/stylesheet.css
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/supported-platforms.html
share/doc/html/postgresql/transaction-iso.html
share/doc/html/postgresql/trigger-datachanges.html
share/doc/html/postgresql/trigger-examples.html
share/doc/html/postgresql/trigger-manager.html
share/doc/html/postgresql/triggers.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/tutorial-accessdb.html
share/doc/html/postgresql/tutorial-advanced.html
share/doc/html/postgresql/tutorial-agg.html
share/doc/html/postgresql/tutorial-arch.html
share/doc/html/postgresql/tutorial-concepts.html
share/doc/html/postgresql/tutorial-conclusion.html
share/doc/html/postgresql/tutorial-createdb.html
share/doc/html/postgresql/tutorial-delete.html
share/doc/html/postgresql/tutorial-fk.html
share/doc/html/postgresql/tutorial-inheritance.html
share/doc/html/postgresql/tutorial-join.html
share/doc/html/postgresql/tutorial-populate.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/tutorial-preface.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/tutorial-select.html
share/doc/html/postgresql/tutorial-sql.html
share/doc/html/postgresql/tutorial-start.html
share/doc/html/postgresql/tutorial-table.html
share/doc/html/postgresql/tutorial-transactions.html
share/doc/html/postgresql/tutorial-update.html
share/doc/html/postgresql/tutorial-views.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/tutorial.html
share/doc/html/postgresql/type-system.html
share/doc/html/postgresql/typeconv-func.html
share/doc/html/postgresql/typeconv-oper.html
share/doc/html/postgresql/typeconv-query.html
share/doc/html/postgresql/typeconv-union-case.html
share/doc/html/postgresql/typeconv.html
share/doc/html/postgresql/units-history.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/unsupported-features-sql99.html
share/doc/html/postgresql/user-attributes.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/user-manag.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/user-preface-thisbook.html
share/doc/html/postgresql/user-preface.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/user.html
share/doc/html/postgresql/wal-configuration.html
share/doc/html/postgresql/wal-implementation.html
share/doc/html/postgresql/wal.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/x11875.html
share/doc/html/postgresql/x1779.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/xaggr.html
share/doc/html/postgresql/xfunc-c.html
share/doc/html/postgresql/xfunc-internal.html
share/doc/html/postgresql/xfunc-overload.html
share/doc/html/postgresql/xfunc-pl.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/xfunc-plhandler.html
share/doc/html/postgresql/xfunc-sql.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/xfunc-tablefunctions.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/xfunc.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/xindex-am.html
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/html/postgresql/xindex-opclass-features.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/xindex-opclass.html
share/doc/html/postgresql/xindex-operators.html
share/doc/html/postgresql/xindex-strategies.html
share/doc/html/postgresql/xindex-support.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/xindex.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/xoper-example.html
share/doc/html/postgresql/xoper-optimization.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/xoper.html
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/html/postgresql/xplang-install.html
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/html/postgresql/xplang.html
share/doc/html/postgresql/xtypes.html
share/doc/postgresql/FAQ
share/doc/postgresql/FAQ_AIX
share/doc/postgresql/FAQ_DEV
share/doc/postgresql/FAQ_HPUX
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
share/doc/postgresql/FAQ_IRIX
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/postgresql/FAQ_MSWIN
share/doc/postgresql/FAQ_QNX4
share/doc/postgresql/FAQ_SCO
share/doc/postgresql/FAQ_Solaris
share/doc/postgresql/FAQ_german
share/doc/postgresql/FAQ_japanese
Updated databases/postgresql to 7.3.1. ================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2003-01-05 21:12:07 +01:00
share/doc/postgresql/FAQ_polish
Fix PLIST for postgresql 7.2.1.
2002-04-06 11:41:03 +02:00
share/doc/postgresql/FAQ_russian
postgresql-docs: PostgreSQL HTML documentation
2001-05-14 16:46:22 +02:00
share/doc/postgresql/KNOWN_BUGS
share/doc/postgresql/MISSING_FEATURES
share/doc/postgresql/README.mb.big5
share/doc/postgresql/README.mb.jp
share/doc/postgresql/TODO
share/doc/postgresql/bug.template
@dirrm share/doc/postgresql
@dirrm share/doc/html/postgresql
Reference in a new issue Copy permalink