目录搜索
前言何为PostgreSQL?PostgreSQL简史格式约定更多信息臭虫汇报指导I. 教程章1. 从头开始1.1. 安装1.2. 体系基本概念1.3. 创建一个数据库1.4. 访问数据库章2. SQL语言2.1. 介绍2.2. 概念2.3. 创建新表2.4. 向表中添加行2.5. 查询一个表2.6. 表间链接2.7. 聚集函数2.8. 更新2.9. 删除章3. 高级特性3.1. 介绍3.2. 视图3.3. 外键3.4. 事务3.5. 窗口函数3.6. 继承3.7. 结论II. SQL语言章4. SQL语法4.1. 词法结构4.2. 值表达式4.3. 调用函数章5. 数据定义5.1. 表的基本概念5.2. 缺省值5.3. 约束5.4. 系统字段5.5. 修改表5.6. 权限5.7. 模式5.8. 继承5.9. 分区5.10. 其它数据库对象5.11. 依赖性跟踪章 6. 数据操作6.1. 插入数据6.2. 更新数据6.3. 删除数据章7. 查询7.1. 概述7.2. 表表达式7.3. 选择列表7.4. 组合查询7.5. 行排序7.6. LIMIT和OFFSET7.7. VALUES列表7.8. WITH的查询(公用表表达式)章8. 数据类型8.1. 数值类型8.2. 货币类型8.3. 字符类型8.4. 二进制数据类型8.5. 日期/时间类型8.6. 布尔类型8.7. 枚举类型8.8. 几何类型8.9. 网络地址类型8.10. 位串类型8.11. 文本搜索类型8.12. UUID类型8.13. XML类型8.14. 数组8.15. 复合类型8.16. 对象标识符类型8.17. 伪类型章 9. 函数和操作符9.1. 逻辑操作符9.2. 比较操作符9.3. 数学函数和操作符9.4. 字符串函数和操作符9.5. 二进制字符串函数和操作符9.6. 位串函数和操作符9.7. 模式匹配9.8. 数据类型格式化函数9.9. 时间/日期函数和操作符9.10. 支持枚举函数9.11. 几何函数和操作符9.12. 网络地址函数和操作符9.13. 文本检索函数和操作符9.14. XML函数9.15. 序列操作函数9.16. 条件表达式9.17. 数组函数和操作符9.18. 聚合函数9.19. 窗口函数9.20. 子查询表达式9.21. 行和数组比较9.22. 返回集合的函数9.23. 系统信息函数9.24. 系统管理函数9.25. 触发器函数章10. 类型转换10.3. 函数10.2. 操作符10.1. 概述10.4. 值存储10.5. UNION章11. 索引11.1. 介绍11.2. 索引类型11.3. 多字段索引11.4. 索引和ORDER BY11.5. 组合多个索引11.6. 唯一索引11.7. 表达式上的索引11.8. 部分索引11.9. 操作类和操作簇11.10. 检查索引的使用章12. Full Text Search12.1. Introduction12.2. Tables and Indexes12.3. Controlling Text Search12.4. Additional Features12.5. Parsers12.6. Dictionaries12.7. Configuration Example12.8. Testing and Debugging Text Search12.9. GiST and GIN Index Types12.10. psql Support12.11. Limitations12.12. Migration from Pre-8.3 Text Search章13. 并发控制13.1. 介绍13.2. 事务隔离13.3. 明确锁定13.4. 应用层数据完整性检查13.5. 锁和索引章14. 性能提升技巧14.1. 使用EXPLAIN14.2. 规划器使用的统计信息14.3. 用明确的JOIN语句控制规划器14.4. 向数据库中添加记录14.5. 非持久性设置III. 服务器管理章15. 安装指导15.1. 简版15.2. 要求15.3. 获取源码15.4. 升级15.5. 安装过程15.6. 安装后的设置15.7. 支持的平台15.8. 特殊平台的要求章16. Installation from Source Code on Windows16.1. Building with Visual C++ or the Platform SDK16.2. Building libpq with Visual C++ or Borland C++章17. 服务器安装和操作17.1. PostgreSQL用户帐户17.2. 创建数据库集群17.3. 启动数据库服务器17.4. 管理内核资源17.5. 关闭服务17.6. 防止服务器欺骗17.7. 加密选项17.8. 用SSL进行安全的TCP/IP连接17.9. Secure TCP/IP Connections with SSH Tunnels章18. 服务器配置18.1. 设置参数18.2. 文件位置18.3. 连接和认证18.4. 资源消耗18.5. 预写式日志18.6. 查询规划18.7. 错误报告和日志18.8. 运行时统计18.9. 自动清理18.10. 客户端连接缺省18.12. 版本和平台兼容性18.11. 锁管理18.13. 预置选项18.14. 自定义的选项18.15. 开发人员选项18.16. 短选项章19. 用户认证19.1. pg_hba.conf 文件19.2. 用户名映射19.3. 认证方法19.4. 用户认证章20. 数据库角色和权限20.1. 数据库角色20.2. 角色属性20.3. 权限20.4. 角色成员20.5. 函数和触发器章21. 管理数据库21.1. 概述21.2. 创建一个数据库21.3. 临时库21.4. 数据库配置21.5. 删除数据库21.6. 表空间章22. 本土化22.1. 区域支持22.2. 字符集支持章23. 日常数据库维护工作23.1. Routine Vacuuming日常清理23.2. 经常重建索引23.3. 日志文件维护章24. 备份和恢复24.1. SQL转储24.2. 文件系统级别的备份24.3. 在线备份以及即时恢复(PITR)24.4. 版本间迁移章25. 高可用性与负载均衡,复制25.1. 不同解决方案的比较25.2. 日志传送备份服务器25.3. 失效切换25.4. 日志传送的替代方法25.5. 热备章26. 恢复配置26.1. 归档恢复设置26.2. 恢复目标设置26.3. 备服务器设置章27. 监控数据库的活动27.1. 标准Unix工具27.2. 统计收集器27.3. 查看锁27.4. 动态跟踪章28. 监控磁盘使用情况28.1. 判断磁盘的使用量28.2. 磁盘满导致的失效章29. 可靠性和预写式日志29.1. 可靠性29.2. 预写式日志(WAL)29.3. 异步提交29.4. WAL配置29.5. WAL内部章30. Regression Tests30.1. Running the Tests30.2. Test Evaluation30.3. Variant Comparison Files30.4. Test Coverage ExaminationIV. 客户端接口章31. libpq-C库31.1. 数据库联接函数31.2. 连接状态函数31.3. 命令执行函数31.4. 异步命令处理31.5. 取消正在处理的查询31.6. 捷径接口31.7. 异步通知31.8. 与COPY命令相关的函数31.9. Control Functions 控制函数31.10. 其他函数31.11. 注意信息处理31.12. 事件系统31.13. 环境变量31.14. 口令文件31.15. 连接服务的文件31.16. LDAP查找连接参数31.17. SSL支持31.18. 在多线程程序里的行为31.19. 制作libpq程序31.20. 例子程序章32. 大对象32.1. 介绍32.2. 实现特点32.3. 客户端接口32.4. 服务器端函数32.5. 例子程序章33. ECPG - Embedded SQL in C33.1. The Concept33.2. Connecting to the Database Server33.3. Closing a Connection33.4. Running SQL Commands33.5. Choosing a Connection33.6. Using Host Variables33.7. Dynamic SQL33.8. pgtypes library33.9. Using Descriptor Areas33.10. Informix compatibility mode33.11. Error Handling33.12. Preprocessor directives33.13. Processing Embedded SQL Programs33.14. Library Functions33.15. Internals章34. 信息模式34.1. 关于这个模式34.2. 数据类型34.3. information_schema_catalog_name34.4. administrable_role_authorizations34.5. applicable_roles34.6. attributes34.7. check_constraint_routine_usage34.8. check_constraints34.9. column_domain_usage34.10. column_privileges34.11. column_udt_usage34.12. 字段34.13. constraint_column_usage34.14. constraint_table_usage34.15. data_type_privileges34.16. domain_constraints34.18. domains34.17. domain_udt_usage34.19. element_types34.20. enabled_roles34.21. foreign_data_wrapper_options34.22. foreign_data_wrappers34.23. foreign_server_options34.24. foreign_servers34.25. key_column_usage34.26. parameters34.27. referential_constraints34.28. role_column_grants34.29. role_routine_grants34.30. role_table_grants34.31. role_usage_grants34.32. routine_privileges34.33. routines34.34. schemata34.35. sequences34.36. sql_features34.37. sql_implementation_info34.38. sql_languages34.39. sql_packages34.40. sql_parts34.41. sql_sizing34.42. sql_sizing_profiles34.43. table_constraints34.44. table_privileges34.45. tables34.46. triggered_update_columns34.47. 触发器34.48. usage_privileges34.49. user_mapping_options34.50. user_mappings34.51. view_column_usage34.52. view_routine_usage34.53. view_table_usage34.54. 视图V. 服务器端编程章35. 扩展SQL35.1. 扩展性是如何实现的35.2. PostgreSQL类型系统35.3. User-Defined Functions35.4. Query Language (SQL) Functions35.5. Function Overloading35.6. Function Volatility Categories35.7. Procedural Language Functions35.8. Internal Functions35.9. C-Language Functions35.10. User-Defined Aggregates35.11. User-Defined Types35.12. User-Defined Operators35.13. Operator Optimization Information35.14. Interfacing Extensions To Indexes35.15. 用C++扩展章36. 触发器36.1. 触发器行为概述36.3. 用 C 写触发器36.2. 数据改变的可视性36.4. 一个完整的例子章37. 规则系统37.1. The Query Tree37.2. 视图和规则系统37.3. 在INSERT,UPDATE和DELETE上的规则37.4. 规则和权限37.5. 规则和命令状态37.6. 规则与触发器得比较章38. Procedural Languages38.1. Installing Procedural Languages章39. PL/pgSQL - SQL过程语言39.1. 概述39.2. PL/pgSQL的结构39.3. 声明39.4. 表达式39.5. 基本语句39.6. 控制结构39.7. 游标39.8. 错误和消息39.9. 触发器过程39.10. PL/pgSQL Under the Hood39.11. 开发PL/pgSQL的一些提示39.12. 从OraclePL/SQL 进行移植章40. PL/Tcl - Tcl Procedural Language40.1. Overview40.2. PL/Tcl Functions and Arguments40.3. Data Values in PL/Tcl40.4. Global Data in PL/Tcl40.5. Database Access from PL/Tcl40.6. Trigger Procedures in PL/Tcl40.7. Modules and the unknown command40.8. Tcl Procedure Names章41. PL/Perl - Perl Procedural Language41.1. PL/Perl Functions and Arguments41.2. Data Values in PL/Perl41.3. Built-in Functions41.4. Global Values in PL/Perl41.6. PL/Perl Triggers41.5. Trusted and Untrusted PL/Perl41.7. PL/Perl Under the Hood章42. PL/Python - Python Procedural Language42.1. Python 2 vs. Python 342.2. PL/Python Functions42.3. Data Values42.4. Sharing Data42.5. Anonymous Code Blocks42.6. Trigger Functions42.7. Database Access42.8. Utility Functions42.9. Environment Variables章43. Server Programming Interface43.1. Interface FunctionsSpi-spi-connectSpi-spi-finishSpi-spi-pushSpi-spi-popSpi-spi-executeSpi-spi-execSpi-spi-execute-with-argsSpi-spi-prepareSpi-spi-prepare-cursorSpi-spi-prepare-paramsSpi-spi-getargcountSpi-spi-getargtypeidSpi-spi-is-cursor-planSpi-spi-execute-planSpi-spi-execute-plan-with-paramlistSpi-spi-execpSpi-spi-cursor-openSpi-spi-cursor-open-with-argsSpi-spi-cursor-open-with-paramlistSpi-spi-cursor-findSpi-spi-cursor-fetchSpi-spi-cursor-moveSpi-spi-scroll-cursor-fetchSpi-spi-scroll-cursor-moveSpi-spi-cursor-closeSpi-spi-saveplan43.2. Interface Support FunctionsSpi-spi-fnameSpi-spi-fnumberSpi-spi-getvalueSpi-spi-getbinvalSpi-spi-gettypeSpi-spi-gettypeidSpi-spi-getrelnameSpi-spi-getnspname43.3. Memory ManagementSpi-spi-pallocSpi-reallocSpi-spi-pfreeSpi-spi-copytupleSpi-spi-returntupleSpi-spi-modifytupleSpi-spi-freetupleSpi-spi-freetupletableSpi-spi-freeplan43.4. Visibility of Data Changes43.5. ExamplesVI. 参考手册I. SQL命令Sql-abortSql-alteraggregateSql-alterconversionSql-alterdatabaseSql-alterdefaultprivilegesSql-alterdomainSql-alterforeigndatawrapperSql-alterfunctionSql-altergroupSql-alterindexSql-alterlanguageSql-alterlargeobjectSql-alteroperatorSql-alteropclassSql-alteropfamilySql-alterroleSql-alterschemaSql-altersequenceSql-alterserverSql-altertableSql-altertablespaceSql-altertsconfigSql-altertsdictionarySql-altertsparserSql-altertstemplateSql-altertriggerSql-altertypeSql-alteruserSql-alterusermappingSql-alterviewSql-analyzeSql-beginSql-checkpointSql-closeSql-clusterSql-commentSql-commitSql-commit-preparedSql-copySql-createaggregateSql-createcastSql-createconstraintSql-createconversionSql-createdatabaseSql-createdomainSql-createforeigndatawrapperSql-createfunctionSql-creategroupSql-createindexSql-createlanguageSql-createoperatorSql-createopclassSql-createopfamilySql-createroleSql-createruleSql-createschemaSql-createsequenceSql-createserverSql-createtableSql-createtableasSql-createtablespaceSql-createtsconfigSql-createtsdictionarySql-createtsparserSql-createtstemplateSql-createtriggerSql-createtypeSql-createuserSql-createusermappingSql-createviewSql-deallocateSql-declareSql-deleteSql-discardSql-doSql-dropaggregateSql-dropcastSql-dropconversionSql-dropdatabaseSql-dropdomainSql-dropforeigndatawrapperSql-dropfunctionSql-dropgroupSql-dropindexSql-droplanguageSql-dropoperatorSql-dropopclassSql-dropopfamilySql-drop-ownedSql-droproleSql-dropruleSql-dropschemaSql-dropsequenceSql-dropserverSql-droptableSql-droptablespaceSql-droptsconfigSql-droptsdictionarySql-droptsparserSql-droptstemplateSql-droptriggerSql-droptypeSql-dropuserSql-dropusermappingSql-dropviewSql-endSql-executeSql-explainSql-fetchSql-grantSql-insertSql-listenSql-loadSql-lockSql-moveSql-notifySql-prepareSql-prepare-transactionSql-reassign-ownedSql-reindexSql-release-savepointSql-resetSql-revokeSql-rollbackSql-rollback-preparedSql-rollback-toSql-savepointSql-selectSql-selectintoSql-setSql-set-constraintsSql-set-roleSql-set-session-authorizationSql-set-transactionSql-showSql-start-transactionSql-truncateSql-unlistenSql-updateSql-vacuumSql-valuesII. 客户端应用程序App-clusterdbApp-createdbApp-createlangApp-createuserApp-dropdbApp-droplangApp-dropuserApp-ecpgApp-pgconfigApp-pgdumpApp-pg-dumpallApp-pgrestoreApp-psqlApp-reindexdbApp-vacuumdbIII. PostgreSQL服务器应用程序App-initdbApp-pgcontroldataApp-pg-ctlApp-pgresetxlogApp-postgresApp-postmasterVII. 内部章44. PostgreSQL内部概览44.1. 查询路径44.2. 连接是如何建立起来的44.3. 分析器阶段44.4. ThePostgreSQL规则系统44.5. 规划器/优化器44.6. 执行器章45. 系统表45.1. 概述45.2. pg_aggregate45.3. pg_am45.4. pg_amop45.5. pg_amproc45.6. pg_attrdef45.7. pg_attribute45.8. pg_authid45.9. pg_auth_members45.10. pg_cast45.11. pg_class45.12. pg_constraint45.13. pg_conversion45.14. pg_database45.15. pg_db_role_setting45.16. pg_default_acl45.17. pg_depend45.18. pg_description45.19. pg_enum45.20. pg_foreign_data_wrapper45.21. pg_foreign_server45.22. pg_index45.23. pg_inherits45.24. pg_language45.25. pg_largeobject45.26. pg_largeobject_metadata45.27. pg_namespace45.28. pg_opclass45.29. pg_operator45.30. pg_opfamily45.31. pg_pltemplate45.32. pg_proc45.33. pg_rewrite45.34. pg_shdepend45.35. pg_shdescription45.36. pg_statistic45.37. pg_tablespace45.38. pg_trigger45.39. pg_ts_config45.40. pg_ts_config_map45.41. pg_ts_dict45.42. pg_ts_parser45.43. pg_ts_template45.44. pg_type45.45. pg_user_mapping45.46. System Views45.47. pg_cursors45.48. pg_group45.49. pg_indexes45.50. pg_locks45.51. pg_prepared_statements45.52. pg_prepared_xacts45.53. pg_roles45.54. pg_rules45.55. pg_settings45.56. pg_shadow45.57. pg_stats45.58. pg_tables45.59. pg_timezone_abbrevs45.60. pg_timezone_names45.61. pg_user45.62. pg_user_mappings45.63. pg_views章46. Frontend/Backend Protocol46.1. Overview46.2. Message Flow46.3. Streaming Replication Protocol46.4. Message Data Types46.5. Message Formats46.6. Error and Notice Message Fields46.7. Summary of Changes since Protocol 2.047. PostgreSQL Coding Conventions47.1. Formatting47.2. Reporting Errors Within the Server47.3. Error Message Style Guide章48. Native Language Support48.1. For the Translator48.2. For the Programmer章49. Writing A Procedural Language Handler章50. Genetic Query Optimizer50.1. Query Handling as a Complex Optimization Problem50.2. Genetic Algorithms50.3. Genetic Query Optimization (GEQO) in PostgreSQL50.4. Further Reading章51. 索引访问方法接口定义51.1. 索引的系统表记录51.2. 索引访问方法函数51.3. 索引扫描51.4. 索引锁的考量51.5. 索引唯一性检查51.6. 索引开销估计函数章52. GiST Indexes52.1. Introduction52.2. Extensibility52.3. Implementation52.4. Examples52.5. Crash Recovery章53. GIN Indexes53.1. Introduction53.2. Extensibility53.3. Implementation53.4. GIN tips and tricks53.5. Limitations53.6. Examples章54. 数据库物理存储54.1. 数据库文件布局54.2. TOAST54.3. 自由空间映射54.4. 可见映射54.5. 数据库分页文件章55. BKI后端接口55.1. BKI 文件格式55.2. BKI命令55.3. 系统初始化的BKI文件的结构55.4. 例子章56. 规划器如何使用统计信息56.1. 行预期的例子VIII. 附录A. PostgreSQL错误代码B. 日期/时间支持B.1. 日期/时间输入解析B.2. 日期/时间关键字B.3. 日期/时间配置文件B.4. 日期单位的历史C. SQL关键字D. SQL ConformanceD.1. Supported FeaturesD.2. Unsupported FeaturesE. Release NotesRelease-0-01Release-0-02Release-0-03Release-1-0Release-1-01Release-1-02Release-1-09Release-6-0Release-6-1Release-6-1-1Release-6-2Release-6-2-1Release-6-3Release-6-3-1Release-6-3-2Release-6-4Release-6-4-1Release-6-4-2Release-6-5Release-6-5-1Release-6-5-2Release-6-5-3Release-7-0Release-7-0-1Release-7-0-2Release-7-0-3Release-7-1Release-7-1-1Release-7-1-2Release-7-1-3Release-7-2Release-7-2-1Release-7-2-2Release-7-2-3Release-7-2-4Release-7-2-5Release-7-2-6Release-7-2-7Release-7-2-8Release-7-3Release-7-3-1Release-7-3-10Release-7-3-11Release-7-3-12Release-7-3-13Release-7-3-14Release-7-3-15Release-7-3-16Release-7-3-17Release-7-3-18Release-7-3-19Release-7-3-2Release-7-3-20Release-7-3-21Release-7-3-3Release-7-3-4Release-7-3-5Release-7-3-6Release-7-3-7Release-7-3-8Release-7-3-9Release-7-4Release-7-4-1Release-7-4-10Release-7-4-11Release-7-4-12Release-7-4-13Release-7-4-14Release-7-4-15Release-7-4-16Release-7-4-17Release-7-4-18Release-7-4-19Release-7-4-2Release-7-4-20Release-7-4-21Release-7-4-22Release-7-4-23Release-7-4-24Release-7-4-25Release-7-4-26Release-7-4-27Release-7-4-28Release-7-4-29Release-7-4-3Release-7-4-30Release-7-4-4Release-7-4-5Release-7-4-6Release-7-4-7Release-7-4-8Release-7-4-9Release-8-0Release-8-0-1Release-8-0-10Release-8-0-11Release-8-0-12Release-8-0-13Release-8-0-14Release-8-0-15Release-8-0-16Release-8-0-17Release-8-0-18Release-8-0-19Release-8-0-2Release-8-0-20Release-8-0-21Release-8-0-22Release-8-0-23Release-8-0-24Release-8-0-25Release-8-0-26Release-8-0-3Release-8-0-4Release-8-0-5Release-8-0-6Release-8-0-7Release-8-0-8Release-8-0-9Release-8-1Release-8-1-1Release-8-1-10Release-8-1-11Release-8-1-12Release-8-1-13Release-8-1-14Release-8-1-15Release-8-1-16Release-8-1-17Release-8-1-18Release-8-1-19Release-8-1-2Release-8-1-20Release-8-1-21Release-8-1-22Release-8-1-23Release-8-1-3Release-8-1-4Release-8-1-5Release-8-1-6Release-8-1-7Release-8-1-8Release-8-1-9Release-8-2Release-8-2-1Release-8-2-10Release-8-2-11Release-8-2-12Release-8-2-13Release-8-2-14Release-8-2-15Release-8-2-16Release-8-2-17Release-8-2-18Release-8-2-19Release-8-2-2Release-8-2-20Release-8-2-21Release-8-2-3Release-8-2-4Release-8-2-5Release-8-2-6Release-8-2-7Release-8-2-8Release-8-2-9Release-8-3Release-8-3-1Release-8-3-10Release-8-3-11Release-8-3-12Release-8-3-13Release-8-3-14Release-8-3-15Release-8-3-2Release-8-3-3Release-8-3-4Release-8-3-5Release-8-3-6Release-8-3-7Release-8-3-8Release-8-3-9Release-8-4Release-8-4-1Release-8-4-2Release-8-4-3Release-8-4-4Release-8-4-5Release-8-4-6Release-8-4-7Release-8-4-8Release-9-0Release-9-0-1Release-9-0-2Release-9-0-3Release-9-0-4F. 额外提供的模块F.1. adminpackF.2. auto_explainF.3. btree_ginF.4. btree_gistF.5. chkpassF.6. citextF.7. cubeF.8. dblinkContrib-dblink-connectContrib-dblink-connect-uContrib-dblink-disconnectContrib-dblinkContrib-dblink-execContrib-dblink-openContrib-dblink-fetchContrib-dblink-closeContrib-dblink-get-connectionsContrib-dblink-error-messageContrib-dblink-send-queryContrib-dblink-is-busyContrib-dblink-get-notifyContrib-dblink-get-resultContrib-dblink-cancel-queryContrib-dblink-get-pkeyContrib-dblink-build-sql-insertContrib-dblink-build-sql-deleteContrib-dblink-build-sql-updateF.9. dict_intF.10. dict_xsynF.11. earthdistanceF.12. fuzzystrmatchF.13. hstoreF.14. intaggF.15. intarrayF.16. isnF.17. loF.18. ltreeF.19. oid2nameF.20. pageinspectF.21. passwordcheckF.22. pg_archivecleanupF.23. pgbenchF.24. pg_buffercacheF.25. pgcryptoF.26. pg_freespacemapF.27. pgrowlocksF.28. pg_standbyF.29. pg_stat_statementsF.30. pgstattupleF.31. pg_trgmF.32. pg_upgradeF.33. segF.34. spiF.35. sslinfoF.36. tablefuncF.37. test_parserF.38. tsearch2F.39. unaccentF.40. uuid-osspF.41. vacuumloF.42. xml2G. 外部项目G.1. 客户端接口G.2. 过程语言G.3. 扩展H. The Source Code RepositoryH.1. Getting The Source Via GitI. 文档I.1. DocBookI.2. 工具集I.3. 制作文档I.4. 文档写作I.5. 风格指导J. 首字母缩略词参考书目BookindexIndex
文字

E.14. Release 8.4

Release Date: 2009-07-01

E.14.1. Overview

After many years of development, PostgreSQL has become feature-complete in many areas. This release shows a targeted approach to adding features (e.g., authentication, monitoring, space reuse), and adds capabilities defined in the later SQL standards. The major areas of enhancement are:

  • Windowing Functions

  • Common Table Expressions and Recursive Queries

  • Default and variadic parameters for functions

  • Parallel Restore

  • Column Permissions

  • Per-database locale settings

  • Improved hash indexes

  • Improved join performance for EXISTS and NOT EXISTS queries

  • Easier-to-use Warm Standby

  • Automatic sizing of the Free Space Map

  • Visibility Map (greatly reduces vacuum overhead for slowly-changing tables)

  • Version-aware psql (backslash commands work against older servers)

  • Support SSL certificates for user authentication

  • Per-function runtime statistics

  • Easy editing of functions in psql

  • New contrib modules: pg_stat_statements, auto_explain, citext, btree_gin

The above items are explained in more detail in the sections below.

E.14.2. Migration to Version 8.4

A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.

Observe the following incompatibilities:

E.14.2.1. General

  • Use 64-bit integer datetimes by default (Neil Conway)

    Previously this was selected by configure's --enable-integer-datetimes option. To retain the old behavior, build with --disable-integer-datetimes.

  • Remove ipcclean utility command (Bruce)

    The utility only worked on a few platforms. Users should use their operating system tools instead.

E.14.2.2. Server Settings

  • Change default setting for log_min_messages to warning (previously it was notice) to reduce log file volume (Tom)

  • Change default setting for max_prepared_transactions to zero (previously it was 5) (Tom)

  • Make debug_print_parse, debug_print_rewritten, and debug_print_plan output appear at LOG message level, not DEBUG1 as formerly (Tom)

  • Make debug_pretty_print default to on (Tom)

  • Remove explain_pretty_print parameter (no longer needed) (Tom)

  • Make log_temp_files settable by superusers only, like other logging options (Simon Riggs)

  • Remove automatic appending of the epoch timestamp when no % escapes are present in log_filename (Robert Haas)

    This change was made because some users wanted a fixed log filename, for use with an external log rotation tool.

  • Remove log_restartpoints from recovery.conf; instead use log_checkpoints (Simon)

  • Remove krb_realm and krb_server_hostname; these are now set in pg_hba.conf instead (Magnus)

  • There are also significant changes in pg_hba.conf, as described below.

E.14.2.3. Queries

  • Change TRUNCATE and LOCK to apply to child tables of the specified table(s) (Peter)

    These commands now accept an ONLY option that prevents processing child tables; this option must be used if the old behavior is needed.

  • SELECT DISTINCT and UNION/INTERSECT/EXCEPT no longer always produce sorted output (Tom)

    Previously, these types of queries always removed duplicate rows by means of Sort/Unique processing (i.e., sort then remove adjacent duplicates). Now they can be implemented by hashing, which will not produce sorted output. If an application relied on the output being in sorted order, the recommended fix is to add an ORDER BY clause. As a short-term workaround, the previous behavior can be restored by disabling enable_hashagg, but that is a very performance-expensive fix. SELECT DISTINCT ON never uses hashing, however, so its behavior is unchanged.

  • Force child tables to inherit CHECK constraints from parents (Alex Hunsaker, Nikhil Sontakke, Tom)

    Formerly it was possible to drop such a constraint from a child table, allowing rows that violate the constraint to be visible when scanning the parent table. This was deemed inconsistent, as well as contrary to SQL standard.

  • Disallow negative LIMIT or OFFSET values, rather than treating them as zero (Simon)

  • Disallow LOCK TABLE outside a transaction block (Tom)

    Such an operation is useless because the lock would be released immediately.

  • Sequences now contain an additional start_value column (Zoltan Boszormenyi)

    This supports ALTER SEQUENCE ... RESTART.

E.14.2.4. Functions and Operators

  • Make numeric zero raised to a fractional power return 0, rather than throwing an error, and make numeric zero raised to the zero power return 1, rather than error (Bruce)

    This matches the longstanding float8 behavior.

  • Allow unary minus of floating-point values to produce minus zero (Tom)

    The changed behavior is more IEEE-standard compliant.

  • Throw an error if an escape character is the last character in a LIKE pattern (i.e., it has nothing to escape) (Tom)

    Previously, such an escape character was silently ignored, thus possibly masking application logic errors.

  • Remove ~=~ and ~<>~ operators formerly used for LIKE index comparisons (Tom)

    Pattern indexes now use the regular equality operator.

  • xpath() now passes its arguments to libxml without any changes (Andrew)

    This means that the XML argument must be a well-formed XML document. The previous coding attempted to allow XML fragments, but it did not work well.

  • Make xmlelement() format attribute values just like content values (Peter)

    Previously, attribute values were formatted according to the normal SQL output behavior, which is sometimes at odds with XML rules.

  • Rewrite memory management for libxml-using functions (Tom)

    This change should avoid some compatibility problems with use of libxml in PL/Perl and other add-on code.

  • Adopt a faster algorithm for hash functions (Kenneth Marshall, based on work of Bob Jenkins)

    Many of the built-in hash functions now deliver different results on little-endian and big-endian platforms.

E.14.2.4.1. Temporal Functions and Operators

  • DateStyle no longer controls interval output formatting; instead there is a new variable IntervalStyle (Ron Mayer)

  • Improve consistency of handling of fractional seconds in timestamp and interval output (Ron Mayer)

    This may result in displaying a different number of fractional digits than before, or rounding instead of truncating.

  • Make to_char()'s localized month/day names depend on LC_TIME, not LC_MESSAGES (Euler Taveira de Oliveira)

  • Cause to_date() and to_timestamp() to more consistently report errors for invalid input (Brendan Jurd)

    Previous versions would often ignore or silently misread input that did not match the format string. Such cases will now result in an error.

  • Fix to_timestamp() to not require upper/lower case matching for meridian (AM/PM) and era (BC/AD) format designations (Brendan Jurd)

    For example, input value ad now matches the format string AD.

E.14.3. Changes

Below you will find a detailed account of the changes between PostgreSQL 8.4 and the previous major release.

E.14.3.1. Performance

  • Improve optimizer statistics calculations (Jan Urbanski, Tom)

    In particular, estimates for full-text-search operators are greatly improved.

  • Allow SELECT DISTINCT and UNION/INTERSECT/EXCEPT to use hashing (Tom)

    This means that these types of queries no longer automatically produce sorted output.

  • Create explicit concepts of semi-joins and anti-joins (Tom)

    This work formalizes our previous ad-hoc treatment of IN (SELECT ...) clauses, and extends it to EXISTS and NOT EXISTS clauses. It should result in significantly better planning of EXISTS and NOT EXISTS queries. In general, logically equivalent IN and EXISTS clauses should now have similar performance, whereas previously IN often won.

  • Improve optimization of sub-selects beneath outer joins (Tom)

    Formerly, a sub-select or view could not be optimized very well if it appeared within the nullable side of an outer join and contained non-strict expressions (for instance, constants) in its result list.

  • Improve the performance of text_position() and related functions by using Boyer-Moore-Horspool searching (David Rowley)

    This is particularly helpful for long search patterns.

  • Reduce I/O load of writing the statistics collection file by writing the file only when requested (Martin Pihlak)

  • Improve performance for bulk inserts (Robert Haas, Simon)

  • Increase the default value of default_statistics_target from 10 to 100 (Greg Sabino Mullane, Tom)

    The maximum value was also increased from 1000 to 10000.

  • Perform constraint_exclusion checking by default in queries involving inheritance or UNION ALL (Tom)

    A new constraint_exclusion setting, partition, was added to specify this behavior.

  • Allow I/O read-ahead for bitmap index scans (Greg Stark)

    The amount of read-ahead is controlled by effective_io_concurrency. This feature is available only if the kernel has posix_fadvise() support.

  • Inline simple set-returning SQL functions in FROM clauses (Richard Rowell)

  • Improve performance of multi-batch hash joins by providing a special case for join key values that are especially common in the outer relation (Bryce Cutt, Ramon Lawrence)

  • Reduce volume of temporary data in multi-batch hash joins by suppressing "physical tlist" optimization (Michael Henderson, Ramon Lawrence)

  • Avoid waiting for idle-in-transaction sessions during CREATE INDEX CONCURRENTLY (Simon)

  • Improve performance of shared cache invalidation (Tom)

E.14.3.2. Server

E.14.3.2.1. Settings

  • Convert many postgresql.conf settings to enumerated values so that pg_settings can display the valid values (Magnus)

  • Add cursor_tuple_fraction parameter to control the fraction of a cursor's rows that the planner assumes will be fetched (Robert Hell)

  • Allow underscores in the names of custom variable classes in postgresql.conf (Tom)

E.14.3.2.2. Authentication and security

  • Remove support for the (insecure) crypt authentication method (Magnus)

    This effectively obsoletes pre-PostgreSQL 7.2 client libraries, as there is no longer any non-plaintext password method that they can use.

  • Support regular expressions in pg_ident.conf (Magnus)

  • Allow Kerberos/GSSAPI parameters to be changed without restarting the postmaster (Magnus)

  • Support SSL certificate chains in server certificate file (Andrew Gierth)

    Including the full certificate chain makes the client able to verify the certificate without having all intermediate CA certificates present in the local store, which is often the case for commercial CAs.

  • Report appropriate error message for combination of MD5 authentication and db_user_namespace enabled (Bruce)

E.14.3.2.3. pg_hba.conf

  • Change all authentication options to use name=value syntax (Magnus)

    This makes incompatible changes to the ldap, pam and ident authentication methods. All pg_hba.conf entries with these methods need to be rewritten using the new format.

  • Remove the ident sameuser option, instead making that behavior the default if no usermap is specified (Magnus)

  • Allow a usermap parameter for all external authentication methods (Magnus)

    Previously a usermap was only supported for ident authentication.

  • Add clientcert option to control requesting of a client certificate (Magnus)

    Previously this was controlled by the presence of a root certificate file in the server's data directory.

  • Add cert authentication method to allow user authentication via SSL certificates (Magnus)

    Previously SSL certificates could only verify that the client had access to a certificate, not authenticate a user.

  • Allow krb5, gssapi and sspi realm and krb5 host settings to be specified in pg_hba.conf (Magnus)

    These override the settings in postgresql.conf.

  • Add include_realm parameter for krb5, gssapi, and sspi methods (Magnus)

    This allows identical usernames from different realms to be authenticated as different database users using usermaps.

  • Parse pg_hba.conf fully when it is loaded, so that errors are reported immediately (Magnus)

    Previously, most errors in the file wouldn't be detected until clients tried to connect, so an erroneous file could render the system unusable. With the new behavior, if an error is detected during reload then the bad file is rejected and the postmaster continues to use its old copy.

  • Show all parsing errors in pg_hba.conf instead of aborting after the first one (Selena Deckelmann)

  • Support ident authentication over Unix-domain sockets on Solaris (Garick Hamlin)

E.14.3.2.4. Continuous Archiving

  • Provide an option to pg_start_backup() to force its implied checkpoint to finish as quickly as possible (Tom)

    The default behavior avoids excess I/O consumption, but that is pointless if no concurrent query activity is going on.

  • Make pg_stop_backup() wait for modified WAL files to be archived (Simon)

    This guarantees that the backup is valid at the time pg_stop_backup() completes.

  • When archiving is enabled, rotate the last WAL segment at shutdown so that all transactions can be archived immediately (Guillaume Smet, Heikki)

  • Delay "smart" shutdown while a continuous archiving base backup is in progress (Laurenz Albe)

  • Cancel a continuous archiving base backup if "fast" shutdown is requested (Laurenz Albe)

  • Allow recovery.conf boolean variables to take the same range of string values as postgresql.conf boolean variables (Bruce)

E.14.3.2.5. Monitoring

  • Add pg_conf_load_time() to report when the PostgreSQL configuration files were last loaded (George Gensure)

  • Add pg_terminate_backend() to safely terminate a backend (the SIGTERM signal works also) (Tom, Bruce)

    While it's always been possible to SIGTERM a single backend, this was previously considered unsupported; and testing of the case found some bugs that are now fixed.

  • Add ability to track user-defined functions' call counts and runtimes (Martin Pihlak)

    Function statistics appear in a new system view, pg_stat_user_functions. Tracking is controlled by the new parameter track_functions.

  • Allow specification of the maximum query string size in pg_stat_activity via new track_activity_query_size parameter (Thomas Lee)

  • Increase the maximum line length sent to syslog, in hopes of improving performance (Tom)

  • Add read-only configuration variables segment_size, wal_block_size, and wal_segment_size (Bernd Helmle)

  • When reporting a deadlock, report the text of all queries involved in the deadlock to the server log (Itagaki Takahiro)

  • Add pg_stat_get_activity(pid) function to return information about a specific process id (Magnus)

  • Allow the location of the server's statistics file to be specified via stats_temp_directory (Magnus)

    This allows the statistics file to be placed in a RAM-resident directory to reduce I/O requirements. On startup/shutdown, the file is copied to its traditional location ($PGDATA/global/) so it is preserved across restarts.

E.14.3.3. Queries

  • Add support for WINDOW functions (Hitoshi Harada)

  • Add support for WITH clauses (CTEs), including WITH RECURSIVE (Yoshiyuki Asaba, Tatsuo Ishii, Tom)

  • Add TABLE command (Peter)

    TABLE tablename is a SQL standard short-hand for SELECT * FROM tablename.

  • Allow AS to be optional when specifying a SELECT (or RETURNING) column output label (Hiroshi Saito)

    This works so long as the column label is not any PostgreSQL keyword; otherwise AS is still needed.

  • Support set-returning functions in SELECT result lists even for functions that return their result via a tuplestore (Tom)

    In particular, this means that functions written in PL/pgSQL and other PL languages can now be called this way.

  • Support set-returning functions in the output of aggregation and grouping queries (Tom)

  • Allow SELECT FOR UPDATE/SHARE to work on inheritance trees (Tom)

  • Add infrastructure for SQL/MED (Martin Pihlak, Peter)

    There are no remote or external SQL/MED capabilities yet, but this change provides a standardized and future-proof system for managing connection information for modules like dblink and plproxy.

  • Invalidate cached plans when referenced schemas, functions, operators, or operator classes are modified (Martin Pihlak, Tom)

    This improves the system's ability to respond to on-the-fly DDL changes.

  • Allow comparison of composite types and allow arrays of anonymous composite types (Tom)

    This allows constructs such as row(1, 1.1) = any (array[row(7, 7.7), row(1, 1.0)]). This is particularly useful in recursive queries.

  • Add support for Unicode string literal and identifier specifications using code points, e.g. U&'d\0061t\+000061' (Peter)

  • Reject \000 in string literals and COPY data (Tom)

    Previously, this was accepted but had the effect of terminating the string contents.

  • Improve the parser's ability to report error locations (Tom)

    An error location is now reported for many semantic errors, such as mismatched datatypes, that previously could not be localized.

E.14.3.3.1. TRUNCATE

  • Support statement-level ON TRUNCATE triggers (Simon)

  • Add RESTART/CONTINUE IDENTITY options for TRUNCATE TABLE (Zoltan Boszormenyi)

    The start value of a sequence can be changed by ALTER SEQUENCE START WITH.

  • Allow TRUNCATE tab1, tab1 to succeed (Bruce)

  • Add a separate TRUNCATE permission (Robert Haas)

E.14.3.3.2. EXPLAIN

  • Make EXPLAIN VERBOSE show the output columns of each plan node (Tom)

    Previously EXPLAIN VERBOSE output an internal representation of the query plan. (That behavior is now available via debug_print_plan.)

  • Make EXPLAIN identify subplans and initplans with individual labels (Tom)

  • Make EXPLAIN honor debug_print_plan (Tom)

  • Allow EXPLAIN on CREATE TABLE AS (Peter)

E.14.3.3.3. LIMIT/OFFSET

  • Allow sub-selects in LIMIT and OFFSET (Tom)

  • Add SQL-standard syntax for LIMIT/OFFSET capabilities (Peter)

    To wit, OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS} ONLY.

E.14.3.4. Object Manipulation

  • Add support for column-level privileges (Stephen Frost, KaiGai Kohei)

  • Refactor multi-object DROP operations to reduce the need for CASCADE (Alex Hunsaker)

    For example, if table B has a dependency on table A, the command DROP TABLE A, B no longer requires the CASCADE option.

  • Fix various problems with concurrent DROP commands by ensuring that locks are taken before we begin to drop dependencies of an object (Tom)

  • Improve reporting of dependencies during DROP commands (Tom)

  • Add WITH [NO] DATA clause to CREATE TABLE AS, per the SQL standard (Peter, Tom)

  • Add support for user-defined I/O conversion casts (Heikki)

  • Allow CREATE AGGREGATE to use an internal transition datatype (Tom)

  • Add LIKE clause to CREATE TYPE (Tom)

    This simplifies creation of data types that use the same internal representation as an existing type.

  • Allow specification of the type category and "preferred" status for user-defined base types (Tom)

    This allows more control over the coercion behavior of user-defined types.

  • Allow CREATE OR REPLACE VIEW to add columns to the end of a view (Robert Haas)

E.14.3.4.1. ALTER

  • Add ALTER TYPE RENAME (Petr Jelinek)

  • Add ALTER SEQUENCE ... RESTART (with no parameter) to reset a sequence to its initial value (Zoltan Boszormenyi)

  • Modify the ALTER TABLE syntax to allow all reasonable combinations for tables, indexes, sequences, and views (Tom)

    This change allows the following new syntaxes:

    • ALTER SEQUENCE OWNER TO

    • ALTER VIEW ALTER COLUMN SET/DROP DEFAULT

    • ALTER VIEW OWNER TO

    • ALTER VIEW SET SCHEMA

    There is no actual new functionality here, but formerly you had to say ALTER TABLE to do these things, which was confusing.

  • Add support for the syntax ALTER TABLE ... ALTER COLUMN ... SET DATA TYPE (Peter)

    This is SQL-standard syntax for functionality that was already supported.

  • Make ALTER TABLE SET WITHOUT OIDS rewrite the table to physically remove OID values (Tom)

    Also, add ALTER TABLE SET WITH OIDS to rewrite the table to add OIDs.

E.14.3.4.2. Database Manipulation

  • Improve reporting of CREATE/DROP/RENAME DATABASE failure when uncommitted prepared transactions are the cause (Tom)

  • Make LC_COLLATE and LC_CTYPE into per-database settings (Radek Strnad, Heikki)

    This makes collation similar to encoding, which was always configurable per database.

  • Improve checks that the database encoding, collation (LC_COLLATE), and character classes (LC_CTYPE) match (Heikki, Tom)

    Note in particular that a new database's encoding and locale settings can be changed only when copying from template0. This prevents possibly copying data that doesn't match the settings.

  • Add ALTER DATABASE SET TABLESPACE to move a database to a new tablespace (Guillaume Lelarge, Bernd Helmle)

E.14.3.5. Utility Operations

  • Add a VERBOSE option to the CLUSTER command and clusterdb (Jim Cox)

  • Decrease memory requirements for recording pending trigger events (Tom)

E.14.3.5.1. Indexes

  • Dramatically improve the speed of building and accessing hash indexes (Tom Raney, Shreya Bhargava)

    This allows hash indexes to be sometimes faster than btree indexes. However, hash indexes are still not crash-safe.

  • Make hash indexes store only the hash code, not the full value of the indexed column (Xiao Meng)

    This greatly reduces the size of hash indexes for long indexed values, improving performance.

  • Implement fast update option for GIN indexes (Teodor, Oleg)

    This option greatly improves update speed at a small penalty in search speed.

  • xxx_pattern_ops indexes can now be used for simple equality comparisons, not only for LIKE (Tom)

E.14.3.5.2. Full Text Indexes

  • Remove the requirement to use @@@ when doing GIN weighted lookups on full text indexes (Tom, Teodor)

    The normal @@ text search operator can be used instead.

  • Add an optimizer selectivity function for @@ text search operations (Jan Urbanski)

  • Allow prefix matching in full text searches (Teodor Sigaev, Oleg Bartunov)

  • Support multi-column GIN indexes (Teodor Sigaev)

  • Improve support for Nepali language and Devanagari alphabet (Teodor)

E.14.3.5.3. VACUUM

  • Track free space in separate per-relation "fork" files (Heikki)

    Free space discovered by VACUUM is now recorded in *_fsm files, rather than in a fixed-sized shared memory area. The max_fsm_pages and max_fsm_relations settings have been removed, greatly simplifying administration of free space management.

  • Add a visibility map to track pages that do not require vacuuming (Heikki)

    This allows VACUUM to avoid scanning all of a table when only a portion of the table needs vacuuming. The visibility map is stored in per-relation "fork" files.

  • Add vacuum_freeze_table_age parameter to control when VACUUM should ignore the visibility map and do a full table scan to freeze tuples (Heikki)

  • Track transaction snapshots more carefully (Alvaro)

    This improves VACUUM's ability to reclaim space in the presence of long-running transactions.

  • Add ability to specify per-relation autovacuum and TOAST parameters in CREATE TABLE (Alvaro, Euler Taveira de Oliveira)

    Autovacuum options used to be stored in a system table.

  • Add --freeze option to vacuumdb (Bruce)

E.14.3.6. Data Types

  • Add a CaseSensitive option for text search synonym dictionaries (Simon)

  • Improve the precision of NUMERIC division (Tom)

  • Add basic arithmetic operators for int2 with int8 (Tom)

    This eliminates the need for explicit casting in some situations.

  • Allow UUID input to accept an optional hyphen after every fourth digit (Robert Haas)

  • Allow on/off as input for the boolean data type (Itagaki Takahiro)

  • Allow spaces around NaN in the input string for type numeric (Sam Mason)

E.14.3.6.1. Temporal Data Types

  • Reject year 0 BC and years 000 and 0000 (Tom)

    Previously these were interpreted as 1 BC. (Note: years 0 and 00 are still assumed to be the year 2000.)

  • Include SGT (Singapore time) in the default list of known time zone abbreviations (Tom)

  • Support infinity and -infinity as values of type date (Tom)

  • Make parsing of interval literals more standard-compliant (Tom, Ron Mayer)

    For example, INTERVAL '1' YEAR now does what it's supposed to.

  • Allow interval fractional-seconds precision to be specified after the second keyword, for SQL standard compliance (Tom)

    Formerly the precision had to be specified after the keyword interval. (For backwards compatibility, this syntax is still supported, though deprecated.) Data type definitions will now be output using the standard format.

  • Support the IS0 8601 interval syntax (Ron Mayer, Kevin Grittner)

    For example, INTERVAL 'P1Y2M3DT4H5M6.7S' is now supported.

  • Add IntervalStyle parameter which controls how interval values are output (Ron Mayer)

    Valid values are: postgres, postgres_verbose, sql_standard, iso_8601. This setting also controls the handling of negative interval input when only some fields have positive/negative designations.

  • Improve consistency of handling of fractional seconds in timestamp and interval output (Ron Mayer)

E.14.3.6.2. Arrays

  • Improve the handling of casts applied to ARRAY[] constructs, such as ARRAY[...]::integer[] (Brendan Jurd)

    Formerly PostgreSQL attempted to determine a data type for the ARRAY[] construct without reference to the ensuing cast. This could fail unnecessarily in many cases, in particular when the ARRAY[] construct was empty or contained only ambiguous entries such as NULL. Now the cast is consulted to determine the type that the array elements must be.

  • Make SQL-syntax ARRAY dimensions optional to match the SQL standard (Peter)

  • Add array_ndims() to return the number of dimensions of an array (Robert Haas)

  • Add array_length() to return the length of an array for a specified dimension (Jim Nasby, Robert Haas, Peter Eisentraut)

  • Add aggregate function array_agg(), which returns all aggregated values as a single array (Robert Haas, Jeff Davis, Peter)

  • Add unnest(), which converts an array to individual row values (Tom)

    This is the opposite of array_agg().

  • Add array_fill() to create arrays initialized with a value (Pavel Stehule)

  • Add generate_subscripts() to simplify generating the range of an array's subscripts (Pavel Stehule)

E.14.3.6.3. Wide-Value Storage (TOAST)

  • Consider TOAST compression on values as short as 32 bytes (previously 256 bytes) (Greg Stark)

  • Require 25% minimum space savings before using TOAST compression (previously 20% for small values and any-savings-at-all for large values) (Greg)

  • Improve TOAST heuristics for rows that have a mix of large and small toastable fields, so that we prefer to push large values out of line and don't compress small values unnecessarily (Greg, Tom)

E.14.3.7. Functions

  • Document that setseed() allows values from -1 to 1 (not just 0 to 1), and enforce the valid range (Kris Jurka)

  • Add server-side function lo_import(filename, oid) (Tatsuo)

  • Add quote_nullable(), which behaves like quote_literal() but returns the string NULL for a null argument (Brendan Jurd)

  • Improve full text search headline() function to allow extracting several fragments of text (Sushant Sinha)

  • Add suppress_redundant_updates_trigger() trigger function to avoid overhead for non-data-changing updates (Andrew)

  • Add div(numeric, numeric) to perform numeric division without rounding (Tom)

  • Add timestamp and timestamptz versions of generate_series() (Hitoshi Harada)

E.14.3.7.1. Object Information Functions

  • Implement current_query() for use by functions that need to know the currently running query (Tomas Doran)

  • Add pg_get_keywords() to return a list of the parser keywords (Dave Page)

  • Add pg_get_functiondef() to see a function's definition (Abhijit Menon-Sen)

  • Allow the second argument of pg_get_expr() to be zero when deparsing an expression that does not contain variables (Tom)

  • Modify pg_relation_size() to use regclass (Heikki)

    pg_relation_size(data_type_name) no longer works.

  • Add boot_val and reset_val columns to pg_settings output (Greg Smith)

  • Add source file name and line number columns to pg_settings output for variables set in a configuration file (Magnus, Alvaro)

    For security reasons, these columns are only visible to superusers.

  • Add support for CURRENT_CATALOG, CURRENT_SCHEMA, SET CATALOG, SET SCHEMA (Peter)

    These provide SQL-standard syntax for existing features.

  • Add pg_typeof() which returns the data type of any value (Brendan Jurd)

  • Make version() return information about whether the server is a 32- or 64-bit binary (Bruce)

  • Fix the behavior of information schema columns is_insertable_into and is_updatable to be consistent (Peter)

  • Improve the behavior of information schema datetime_precision columns (Peter)

    These columns now show zero for date columns, and 6 (the default precision) for time, timestamp, and interval without a declared precision, rather than showing null as formerly.

  • Convert remaining builtin set-returning functions to use OUT parameters (Jaime Casanova)

    This makes it possible to call these functions without specifying a column list: pg_show_all_settings(), pg_lock_status(), pg_prepared_xact(), pg_prepared_statement(), pg_cursor()

  • Make pg_*_is_visible() and has_*_privilege() functions return NULL for invalid OIDs, rather than reporting an error (Tom)

  • Extend has_*_privilege() functions to allow inquiring about the OR of multiple privileges in one call (Stephen Frost, Tom)

  • Add has_column_privilege() and has_any_column_privilege() functions (Stephen Frost, Tom)

E.14.3.7.2. Function Creation

  • Support variadic functions (functions with a variable number of arguments) (Pavel Stehule)

    Only trailing arguments can be optional, and they all must be of the same data type.

  • Support default values for function arguments (Pavel Stehule)

  • Add CREATE FUNCTION ... RETURNS TABLE clause (Pavel Stehule)

  • Allow SQL-language functions to return the output of an INSERT/UPDATE/DELETE RETURNING clause (Tom)

E.14.3.7.3. PL/pgSQL Server-Side Language

  • Support EXECUTE USING for easier insertion of data values into a dynamic query string (Pavel Stehule)

  • Allow looping over the results of a cursor using a FOR loop (Pavel Stehule)

  • Support RETURN QUERY EXECUTE (Pavel Stehule)

  • Improve the RAISE command (Pavel Stehule)

    • Support DETAIL and HINT fields

    • Support specification of the SQLSTATE error code

    • Support an exception name parameter

    • Allow RAISE without parameters in an exception block to re-throw the current error

  • Allow specification of SQLSTATE codes in EXCEPTION lists (Pavel Stehule)

    This is useful for handling custom SQLSTATE codes.

  • Support the CASE statement (Pavel Stehule)

  • Make RETURN QUERY set the special FOUND and GET DIAGNOSTICS ROW_COUNT variables (Pavel Stehule)

  • Make FETCH and MOVE set the GET DIAGNOSTICS ROW_COUNT variable (Andrew Gierth)

  • Make EXIT without a label always exit the innermost loop (Tom)

    Formerly, if there were a BEGIN block more closely nested than any loop, it would exit that block instead. The new behavior matches Oracle(TM) and is also what was previously stated by our own documentation.

  • Make processing of string literals and nested block comments match the main SQL parser's processing (Tom)

    In particular, the format string in RAISE now works the same as any other string literal, including being subject to standard_conforming_strings. This change also fixes other cases in which valid commands would fail when standard_conforming_strings is on.

  • Avoid memory leakage when the same function is called at varying exception-block nesting depths (Tom)

E.14.3.8. Client Applications

  • Fix pg_ctl restart to preserve command-line arguments (Bruce)

  • Add -w/--no-password option that prevents password prompting in all utilities that have a -W/--password option (Peter)

  • Remove -q (quiet) option of createdb, createuser, dropdb, dropuser (Peter)

    These options have had no effect since PostgreSQL 8.3.

E.14.3.8.1. psql

  • Remove verbose startup banner; now just suggest help (Joshua Drake)

  • Make help show common backslash commands (Greg Sabino Mullane)

  • Add \pset format wrapped mode to wrap output to the screen width, or file/pipe output too if \pset columns is set (Bryce Nesbitt)

  • Allow all supported spellings of boolean values in \pset, rather than just on and off (Bruce)

    Formerly, any string other than "off" was silently taken to mean true. psql will now complain about unrecognized spellings (but still take them as true).

  • Use the pager for wide output (Bruce)

  • Require a space between a one-letter backslash command and its first argument (Bernd Helmle)

    This removes a historical source of ambiguity.

  • Improve tab completion support for schema-qualified and quoted identifiers (Greg Sabino Mullane)

  • Add optional on/off argument for \timing (David Fetter)

  • Display access control rights on multiple lines (Brendan Jurd, Andreas Scherbaum)

  • Make \l show database access privileges (Andrew Gilligan)

  • Make \l+ show database sizes, if permissions allow (Andrew Gilligan)

  • Add the \ef command to edit function definitions (Abhijit Menon-Sen)

E.14.3.8.2. psql \d* commands

  • Make \d* commands that do not have a pattern argument show system objects only if the S modifier is specified (Greg Sabino Mullane, Bruce)

    The former behavior was inconsistent across different variants of \d, and in most cases it provided no easy way to see just user objects.

  • Improve \d* commands to work with older PostgreSQL server versions (back to 7.4), not only the current server version (Guillaume Lelarge)

  • Make \d show foreign-key constraints that reference the selected table (Kenneth D'Souza)

  • Make \d on a sequence show its column values (Euler Taveira de Oliveira)

  • Add column storage type and other relation options to the \d+ display (Gregory Stark, Euler Taveira de Oliveira)

  • Show relation size in \dt+ output (Dickson S. Guedes)

  • Show the possible values of enum types in \dT+ (David Fetter)

  • Allow \dC to accept a wildcard pattern, which matches either datatype involved in the cast (Tom)

  • Add a function type column to \df's output, and add options to list only selected types of functions (David Fetter)

  • Make \df not hide functions that take or return type cstring (Tom)

    Previously, such functions were hidden because most of them are datatype I/O functions, which were deemed uninteresting. The new policy about hiding system functions by default makes this wart unnecessary.

E.14.3.8.3. pg_dump

  • Add a --no-tablespaces option to pg_dump/pg_dumpall/pg_restore so that dumps can be restored to clusters that have non-matching tablespace layouts (Gavin Roy)

  • Remove -d and -D options from pg_dump and pg_dumpall (Tom)

    These options were too frequently confused with the option to select a database name in other PostgreSQL client applications. The functionality is still available, but you must now spell out the long option name --inserts or --column-inserts.

  • Remove -i/--ignore-version option from pg_dump and pg_dumpall (Tom)

    Use of this option does not throw an error, but it has no effect. This option was removed because the version checks are necessary for safety.

  • Disable statement_timeout during dump and restore (Joshua Drake)

  • Add pg_dump/pg_dumpall option --lock-wait-timeout (David Gould)

    This allows dumps to fail if unable to acquire a shared lock within the specified amount of time.

  • Reorder pg_dump --data-only output to dump tables referenced by foreign keys before the referencing tables (Tom)

    This allows data loads when foreign keys are already present. If circular references make a safe ordering impossible, a NOTICE is issued.

  • Allow pg_dump, pg_dumpall, and pg_restore to use a specified role (Benedek L

上一篇:下一篇: