pg_dumpall

说明

描述 pg_dumpall 是一个实用程序，用于写出（ “ 转储 ” ）一个集簇中的所有 PostgreSQL 数据库到一个脚本文件中。该脚本文件包含 SQL 命令，可作为 psql 的输入来恢复这些数据库。它通过对集簇中的每个数据库调用 pg_dump 来实现这一点。 pg_dumpall 还会转储所有数据库共有的全局对象，即数据库角色、表空间以及配置参数的权限授予。（ pg_dump 不会保存这些对象。） 由于 pg_dumpall 会读取所有数据库中的表，因此通常必须以数据库超级用户身份连接，才能生成完整的转储。另外，要执行保存的脚本，也需要具备超级用户权限，这样才能添加角色并创建数据库。 SQL 脚本将写入标准输出。使用 -f / --file 选项或 shell 操作符将其重定向到文件。 pg_dumpall 需要多次连接到 PostgreSQL 服务器（每个数据库一次）。如果使用密码认证，它每次都会提示输入密码。在这种情况下准备一个 ~/.pgpass 文件会比较方便。详见 第 32.16 节 。 警告 恢复转储会导致目标系统执行由源超级用户所选择的任意代码。部分转储和部分恢复也无法限制这一点。如果不信任源超级用户，则在恢复前必须检查转储出的 SQL 语句。注意，执行转储和恢复的客户端并不需要信任源超级用户或目标超级用户。 选项 以下命令行选项控制输出的内容和格式。 -a --data-only 只转储数据，不转储模式（数据定义）或统计信息。 -c --clean 在重新创建之前，输出用于 DROP 所有已转储数据库、角色和表空间的 SQL 命令。当恢复需要覆盖现有集簇时，此选项很有用。如果目标集簇中不存在某些对象，则恢复期间会报告可忽略的错误消息，除非还指定了 --if-exists 。 -E encoding --encoding= encoding 在指定的字符集编码中创建转储。默认情况下，转储将以数据库编码创建。（获得相同结果的另一种方法是将 PGCLIENTENCODING 环境变量设置为所需的转储编码。） -f filename --file=

手册中的可执行程序

pg_dumpall

程序版本

18.6

参考清单

客户端程序

选项定义组

55

用法

pg_dumpall [ connection-option ...] [ option ...]

相关条目

• libpq 连接参数

文档与源码

• 18.6 English manual · app-pg-dumpall.html
• Client applications inventory

版本比较

PostgreSQL 17 → 18: 属性变化。

以下差异保留原始字段名与英文源描述。

--- PostgreSQL 17
+++ PostgreSQL 18
@@ -11,7 +11,7 @@
   ],
   "options": [
     {
-      "description": "Dump only the data, not the schema (data definitions).",
+      "description": "Dump only the data, not the schema (data definitions) or statistics.",
       "names": [
         "-a",
         "--data-only"
@@ -41,13 +41,6 @@
         "--file= filename"
       ],
       "signature": "-f filename --file= filename"
-    },
-    {
-      "description": "Specify a filename from which to read patterns for databases excluded from the dump. The patterns are interpreted according to the same rules as --exclude-database . To read from STDIN , use - as the filename. The --filter option can be specified in conjunction with --exclude-database for excluding databases, and can also be specified more than once for multiple filter files. The file lists one database pattern per row, with the following format: exclude database PATTERN Lines starting with # are considered comments and ignored. Comments can be placed after an object pattern row as well. Blank lines are also ignored. See Patterns for how to perform quoting in patterns.",
-      "names": [
-        "--filter= filename"
-      ],
-      "signature": "--filter= filename"
     },
     {
       "description": "Dump only global objects (roles and tablespaces), no databases.",
@@ -145,7 +138,7 @@
       "signature": "--disable-dollar-quoting"
     },
     {
-      "description": "This option is relevant only when creating a data-only dump. It instructs pg_dumpall to include commands to temporarily disable triggers on the target tables while the data is restored. Use this if you have referential integrity checks or other triggers on the tables that you do not want to invoke during data restore. Presently, the commands emitted for --disable-triggers must be done as superuser. So, you should also specify a superuser name with -S , or preferably be careful to start the resulting script as a superuser.",
+      "description": "This option is relevant only when creating a dump with data and without schema. It instructs pg_dumpall to include commands to temporarily disable triggers on the target tables while the data is restored. Use this if you have referential integrity checks or other triggers on the tables that you do not want to invoke during data restore. Presently, the commands emitted for --disable-triggers must be done as superuser. So, you should also specify a superuser name with -S , or preferably be careful to start the resulting script as a superuser.",
       "names": [
         "--disable-triggers"
       ],
@@ -166,6 +159,13 @@
       "signature": "--extra-float-digits= ndigits"
     },
     {
+      "description": "Specify a filename from which to read patterns for databases excluded from the dump. The patterns are interpreted according to the same rules as --exclude-database . To read from STDIN , use - as the filename. The --filter option can be specified in conjunction with --exclude-database for excluding databases, and can also be specified more than once for multiple filter files. The file lists one database pattern per row, with the following format: exclude database PATTERN Lines starting with # are considered comments and ignored. Comments can be placed after an object pattern row as well. Blank lines are also ignored. See Patterns for how to perform quoting in patterns.",
+      "names": [
+        "--filter= filename"
+      ],
+      "signature": "--filter= filename"
+    },
+    {
       "description": "Use DROP ... IF EXISTS commands to drop objects in --clean mode. This suppresses “ does not exist ” errors that might otherwise be reported. This option is not valid unless --clean is also specified.",
       "names": [
         "--if-exists"
@@ -194,13 +194,27 @@
       "signature": "--lock-wait-timeout= timeout"
     },
     {
-      "description": "Do not dump comments.",
+      "description": "Do not dump COMMENT commands.",
       "names": [
         "--no-comments"
       ],
       "signature": "--no-comments"
     },
     {
+      "description": "Do not dump data.",
+      "names": [
+        "--no-data"
+      ],
+      "signature": "--no-data"
+    },
+    {
+      "description": "Do not dump row security policies.",
+      "names": [
+        "--no-policies"
+      ],
+      "signature": "--no-policies"
+    },
+    {
       "description": "Do not dump publications.",
       "names": [
         "--no-publications"
@@ -215,6 +229,13 @@
       "signature": "--no-role-passwords"
     },
     {
+      "description": "Do not dump schema (data definitions).",
+      "names": [
+        "--no-schema"
+      ],
+      "signature": "--no-schema"
+    },
+    {
       "description": "Do not dump security labels.",
       "names": [
         "--no-security-labels"
@@ -222,6 +243,13 @@
       "signature": "--no-security-labels"
     },
     {
+      "description": "Do not dump statistics. This is the default.",
+      "names": [
+        "--no-statistics"
+      ],
+      "signature": "--no-statistics"
+    },
+    {
       "description": "Do not dump subscriptions.",
       "names": [
         "--no-subscriptions"
@@ -290,6 +318,27 @@
         "--rows-per-insert= nrows"
       ],
       "signature": "--rows-per-insert= nrows"
+    },
+    {
+      "description": "Dump optimizer statistics.",
+      "names": [
+        "--statistics"
+      ],
+      "signature": "--statistics"
+    },
+    {
+      "description": "Dump only the statistics, not the schema (data definitions) or data. Optimizer statistics for tables, materialized views, foreign tables, and indexes are dumped.",
+      "names": [
+        "--statistics-only"
+      ],
+      "signature": "--statistics-only"
+    },
+    {
+      "description": "Include sequence data in the dump. This is the default behavior except when --no-data , --schema-only , or --statistics-only is specified.",
+      "names": [
+        "--sequence-data"
+      ],
+      "signature": "--sequence-data"
     },
     {
       "description": "Output SQL-standard SET SESSION AUTHORIZATION commands instead of ALTER OWNER commands to determine object ownership. This makes the dump more standards compatible, but depending on the history of the objects in the dump, might not restore properly.",

比较已记录的接口与属性，排除来源指纹和构建元数据。某个样本中没有记录，不能据此判断实际引入或移除的版本。

相关条目

• clusterdb
• createdb
• createuser
• dropdb
• dropuser
• ecpg
• pg_amcheck
• pg_basebackup
• pg_combinebackup
• pg_config
• pg_dump
• pg_isready