diff --git a/CN/modules/ROOT/pages/9.adoc b/CN/modules/ROOT/pages/9.adoc index 2432ee47..d0ac4c97 100644 --- a/CN/modules/ROOT/pages/9.adoc +++ b/CN/modules/ROOT/pages/9.adoc @@ -1458,11 +1458,11 @@ pg_dump — 把IvorySQL数据库抽取为一个脚本文件或其他归档文件 只转储数据,而不转储模式(数据定义)。表数据、大对象和序列值都会被转储。这个选项类似于指定 `--section=data`,但是由于历史原因又不完全相同。 -- `-b` `--blobs` +- `-b` `--large-objects` `--blobs`(已弃用) -在转储中包括大对象。这是当 `--schema`、 `--table` 或 `--schema-only` 被指定时的默认行为。因此,只有在请求转储一个特定方案或者表的情况中, `-b` 开关才对向转储中加入大对象有用。注意blobs是被考虑的数据,因此在使用 `--data-only` 时将被包括在内,但在使用 `--schema-only` 时则不会包括。 +在转储中包括大对象。这是除指定 `--schema`、`--table`、`--schema-only`、`--statistics-only` 或 `--no-data` 之外的默认行为。因此,只有在请求转储特定模式或表时,`-b` 开关才对向转储中加入大对象有用。注意大对象被视为数据,因此在使用 `--data-only` 时将被包括在内,但在使用 `--schema-only` 或 `--statistics-only` 时则不会包括。 -- `-B` `--no-blobs` +- `-B` `--no-large-objects` `--no-blobs`(已弃用) 在转储中排除大对象。当同时给定 `-b` 和 `-B` 时,行为是在数据被转储时输出大对象,请参考 `-b` 文档。 @@ -1474,7 +1474,7 @@ pg_dump — 把IvorySQL数据库抽取为一个脚本文件或其他归档文件 使得在输出的开始是一个创建数据库本身并且重新连接到被创建的数据库的命令(通过这种形式的一个脚本,在运行脚本之前你连接的是目标安装中的哪个数据库都没有关系)。如果也指定了 `--clean`,脚本会在重新连接到目标数据库之前先删除它然后再重建。通过 `--create`,输出还会包括数据库的注释(如果有)以及与这个数据库相关的任何配置变量设置,也就是任何提到了这个数据库的 `ALTER DATABASE ... SET ...` 命令和 `ALTER ROLE ... IN DATABASE ... SET ...` 命令。该数据库本身的访问特权也会被转储,除非指定有 `--no-acl`。当发出归档(非文本)输出文件时,这个选项被忽略。对于归档格式,你可以在调用 `pg_restore` 时指定该选项。 -- `-e *pattern*` `-−extension=*pattern*` +- `-e *pattern*` `--extension=*pattern*` 只转储匹配 *`pattern`* 的扩展。 如果未指定此选项,目标数据库中的所有非系统扩展都将被转储。 通过写入多个 `-e` 开关,可以选择多个扩展。 *`pattern`* 参数可以理解为与psql's `\d` 命令使用的规则相同的模式, 所以还可以通过在模式中写入通配符来选择多个扩展。 在使用通配符时,如果需要防止来自扩展通配符的shell,请小心的引用模式。任何由 `pg_extension_config_dump` 注册的配置关系被包括在转储中,如果他的扩展已经被 `-−extension` 指定了。注意当指定了 `-e` ,pg_dump不尝试转储任何所选扩展可能依赖的其他数据库对象。 也就是说,这里不保证指定扩展转储的结果能够由他们自己成功恢复到一个干净的数据库中。 @@ -1562,14 +1562,38 @@ pg_dump版本并退出。 只有在转储具有行安全性的表的内容时,这个选项才相关。默认情况下, pg_dump将把 http://www.postgresql.org/docs/17/runtime-config-client.html#GUC-ROW-SECURITY[row_security] 设置为 off 来确保从该表中转储 出所有的数据。如果用户不具有足够能绕过行安全性的特权,那么会抛出 一个错误这个参数指示pg_dump将 http://www.postgresql.org/docs/17/runtime-config-client.html#GUC-ROW-SECURITY[row_security] 设置为 on,允许用户只转储该表中 它们能够访问到的部分内容。注意如果当前你使用了这个选项,你可能还想得到 `INSERT` 格式的转储,因为恢复期间的 `COPY FROM` 不支持行安全性。 +- `--exclude-extension=*pattern*` + +不转储任何匹配 *`pattern`* 的扩展。该模式按照与 `-e` 相同的规则进行解释。可以多次指定 `--exclude-extension` 以排除匹配多个模式的扩展。当同时给定 `-e` 和 `--exclude-extension` 时,行为是仅转储至少匹配一个 `-e` 开关但不匹配任何 `--exclude-extension` 开关的扩展。如果指定了 `--exclude-extension` 而未指定 `-e`,则匹配 `--exclude-extension` 的扩展将从正常转储中排除。 + +- `--exclude-table-and-children=*pattern*` + +与 `-T`/`--exclude-table` 选项相同,但同时也会排除匹配 *`pattern`* 的表的所有分区或继承子表。 + - `--exclude-table-data=*pattern*` 不转储匹配 *`pattern`* 模式的任何表中的数据。该模式根据 `-t` 的相同规则被解释。`--exclude-table-data` 可以被给定多次来排除匹配多个模式的表。当你需要一个特定表的定义但不想要其中的数据时,这个选项就有用了。要排除数据库中所有表的数据,见 `--schema-only`。 +- `--exclude-table-data-and-children=*pattern*` + +与 `--exclude-table-data` 选项相同,但同时也会排除匹配 *`pattern`* 的表的所有分区或继承子表的数据。 + - `--extra-float-digits=*ndigits*` 在转储浮点数据时使用规定的 `extra_float_digits` 值,而不是最大可用精度。以备份目的生成的常规转储不使用此选项。 +- `--filter=*filename*` + +指定一个文件名,从中读取要包含在转储中或从转储中排除的对象模式。这些模式按照与对应选项相同的规则进行解释:表使用 `-t`/`--table`、`--table-and-children`、`-T`/`--exclude-table` 和 `--exclude-table-and-children`;模式(schema)使用 `-n`/`--schema` 和 `-N`/`--exclude-schema`;外部服务器上的数据使用 `--include-foreign-data`;表数据使用 `--exclude-table-data` 和 `--exclude-table-data-and-children`;扩展使用 `-e`/`--extension` 和 `--exclude-extension`。要从 `STDIN` 读取,请使用 `-` 作为文件名。`--filter` 选项可以与上述用于包含或排除对象的选项一起使用,也可以多次指定以使用多个过滤文件。 ++ +该文件每行列出一个对象模式,格式如下: ++ +`{ include | exclude } { extension | foreign_data | table | table_and_children | table_data | table_data_and_children | schema } *PATTERN*` ++ +第一个关键字指定是要包含还是排除与模式匹配的对象。第二个关键字指定要使用该模式过滤的对象类型:`extension`(扩展,类似于 `-e`/`--extension` 或 `--exclude-extension`)、`foreign_data`(外部服务器上的数据,类似于 `--include-foreign-data`,只能与 `include` 关键字一起使用)、`table`(表,类似于 `-t`/`--table` 或 `-T`/`--exclude-table`)、`table_and_children`(表及其任何分区或继承子表,类似于 `--table-and-children` 或 `--exclude-table-and-children`)、`table_data`(匹配 *`pattern`* 的任何表的表数据,类似于 `--exclude-table-data`,只能与 `exclude` 关键字一起使用)、`table_data_and_children`(匹配 *`pattern`* 的表及其任何分区或继承子表的表数据,类似于 `--exclude-table-data-and-children`,只能与 `exclude` 关键字一起使用)以及 `schema`(模式,类似于 `-n`/`--schema` 或 `-N`/`--exclude-schema`)。 ++ +以 `#` 开头的行被视为注释并被忽略。注释也可以放在对象模式行之后,空行同样会被忽略。 + - `--if-exists` 时间条件性命令(即增加一个 `IF EXISTS` 子句)来清除数据库和其他对象。 只有同时指定了 `--clean` 时,这个选项才可用。 @@ -1594,14 +1618,30 @@ pg_dump版本并退出。 不转储注释。 +- `--no-data` + +不转储数据。 + +- `--no-policies` + +不转储行安全性策略。 + - `--no-publications` 不转储publication。 +- `--no-schema` + +不转储模式(数据定义)。 + - `--no-security-labels` 不转储安全标签。 +- `--no-statistics` + +不转储统计信息。这是默认行为。 + - `--no-subscriptions` 不转储订阅。 @@ -1610,6 +1650,10 @@ pg_dump版本并退出。 默认情况下,`pg_dump` 将等待所有文件被安全地写入磁盘。这个选项会让 `pg_dump` 不等待直接返回,这样会更快,但是也意味着后续的一次操作系统崩溃会让该转储损坏。通常这个选项对测试有用,但是不应该在从生产安装中转储数据时使用。 +- `--no-table-access-method` + +不输出选择表访问方法的命令。通过这个选项,在恢复期间所有对象都将使用默认表访问方法创建。当发出归档(非文本)输出文件时,此选项会被忽略。对于归档格式,你可以在调用 `pg_restore` 时指定该选项。 + - `--no-tablespaces` 不要输出选择表空间的命令。通过这个选项,在恢复期间所有的对象都会被创建在任何作为默认的表空间中。当发出归档(非文本)输出文件时,这个选项被忽略。对于归档格式,你可以在调用 `pg_restore` 时指定该选项。 @@ -1630,6 +1674,10 @@ pg_dump版本并退出。 强制引用所有标识符。当从IvorySQL主版本与pg_dump不同的服务器上转储一个数据库时或者当输出准备载入到一个具有不同主版本的服务器时,推荐使用这个选项。默认情况下,pg_dump只对在其主版本中是被保留词的标识符加上引号。在转储其他版本服务器时,这种默认行为有时会导致兼容性问题,因为那些版本可能具有些许不同的被保留词集合。使用 `--quote-all-identifiers` 能阻止这种问题,但代价是转储脚本更难阅读。 +- `--restrict-key=*restrict_key*` + +使用提供的字符串作为转储输出中的 `psql` `\restrict` 密钥。此选项只能用于纯文本转储,即当 `--format` 设置为 `plain` 或省略 `--format` 选项时。如果未指定 restrict key,`pg_dump` 将在需要时生成一个随机密钥。密钥只能包含字母数字字符。此选项主要用于测试以及需要可重复输出(例如比较转储文件)的场景。不建议在一般场景下使用,因为事先知道密钥的恶意服务器可能会注入任意代码并在运行 `psql` 执行转储输出的机器上执行。 + - `--rows-per-insert=*nrows*` 数据转储为 `INSERT` 命令(而不是 `COPY` )。 控制每个 `INSERT` 命令的最大行数。 指定的值必须大于零。重新加载期间的任何错误都将导致有问题的`INSERT` 相关的行将丢失,而不是整个表内容。 @@ -1638,6 +1686,10 @@ pg_dump版本并退出。 只转储命名节。节的名称可以是 `pre-data`、 `data` 或 `post-data`。这个选项可以被指定多次来选择多个节。默认是转储所有节。数据节包含真正的表数据、大对象内容和序列值。数据后项包括索引、触发器、规则和除了已验证检查约束之外的约束的定义。数据前项包括所有其他数据定义项。 +- `--sequence-data` + +在转储中包含序列数据。这是除指定 `--no-data`、`--schema-only` 或 `--statistics-only` 之外的默认行为。 + - `--serializable-deferrable` 为转储使用一个 `可序列化` 事务,以保证所使用的快照与后来的数据库状态是一致的。但是这样做是在事务流中等待一个点,在该点上不能存在异常,这样就不会有转储失败或者导致其他事务带着 `serialization_failure` 回滚的风险。对于一个只为灾难恢复存在的转储,这个选项没什么益处。如果一个转储被用来在原始数据库持续被更新期间载入一份用于报表或其他只读负载的数据库拷贝时,这个选项就有所帮助。如果没有这个选项,转储可能会反映一个与最终提交事务的任何执行序列都不一致的状态。例如,如果使用了批处理技术,一个批处理在转储中可以显示为关闭,而其中的所有项都不出现。如果 pg_dump 被启动时没有读写事务在活动,则这个选项没有什么不同。如果有读写事务在活动,该转储的启动可能会被延迟一段不确定的时间。一旦开始运行,有没有这个开关的表现是相同的。 @@ -1646,10 +1698,26 @@ pg_dump版本并退出。 在做一个数据库的转储时指定一个同步的快照。在需要把转储和一个逻辑复制槽 或者一个并发会话同步时可以用上这个选项。在并行转储的情况下,将使用这个选项指定的快照名而不是取一个新快照。 +- `--statistics` + +转储优化器统计信息。 + +- `--statistics-only` + +仅转储统计信息,不转储模式(数据定义)或数据。将转储表、物化视图、外部表和索引的优化器统计信息。 + - `--strict-names` 要求每一个扩展( `-e` / `--extension` ),模式( `-n` / `--schema` )和表( `-t` / `--table` )限定符匹配要转储的数据库中至少一个扩展/模式/表。 注意,如果没有找到有这样的扩展/模式/表限定符匹配,即便没有 `--strict-names` ,pg_dump也将生成一个错误。这个选项对 `-N` / `--exclude-schema`、`-T` / `--exclude-table` 或者 `--exclude-table-data` 没有效果。无法匹配任何对象的排除模式不会被当作错误。 +- `--sync-method=*method*` + +当设置为 `fsync`(默认值)时,`pg_dump --format=directory` 将递归打开并同步归档目录中的所有文件。在 Linux 上,可以改用 `syncfs` 请求操作系统同步包含归档目录的整个文件系统。当使用 `--no-sync` 或 `--format` 未设置为 `directory` 时,此选项无效。 + +- `--table-and-children=*pattern*` + +与 `-t`/`--table` 选项相同,但同时也会包含匹配 *`pattern`* 的表的所有分区或继承子表。 + - `--use-set-session-authorization` 输出 SQL-标准的 `SET SESSION AUTHORIZATION` 命令取代 `ALTER OWNER` 命令来确定对象的所有关系。这让该转储更加兼容标准,但是取决于该转储中对象的历史,该转储可能无法正常恢复。而且,一个使用 `SET SESSION AUTHORIZATION` 的转储将一定会要求超级用户特权来正确地恢复,而 `ALTER OWNER` 要求更少的特权。 diff --git a/EN/modules/ROOT/pages/9.adoc b/EN/modules/ROOT/pages/9.adoc index d4b420c6..5de67b41 100644 --- a/EN/modules/ROOT/pages/9.adoc +++ b/EN/modules/ROOT/pages/9.adoc @@ -1482,9 +1482,9 @@ The following command-line options control the content and format of the output. - `-b` `--blobs` - Include large objects in the dump. This is the default behavior except when `--schema`, `--table`, or `--schema-only` is specified. The `-b` switch is therefore only useful to add large objects to dumps where a specific schema or table has been requested. Note that blobs are considered data and therefore will be included when `--data-only` is used, but not when `--schema-only` is. + Include large objects in the dump. This is the default behavior except when `--schema`, `--table`, `--schema-only`, `--statistics-only`, or `--no-data` is specified. The `-b` switch is therefore only useful to add large objects to dumps where a specific schema or table has been requested. Note that large objects are considered data and therefore will be included when `--data-only` is used, but not when `--schema-only` or `--statistics-only` is. -- `-B` `--no-blobs` +- `-B` `--no-large-objects` `--no-blobs` (deprecated) Exclude large objects in the dump.When both `-b` and `-B` are given, the behavior is to output large objects, when data is being dumped, see the `-b` documentation. @@ -1584,14 +1584,38 @@ The following command-line options control the content and format of the output. This option is relevant only when dumping the contents of a table which has row security. By default, pg_dump will set http://www.postgresql.org/docs/17/runtime-config-client.html#GUC-ROW-SECURITY[row_security] to off, to ensure that all data is dumped from the table. If the user does not have sufficient privileges to bypass row security, then an error is thrown. This parameter instructs pg_dump to set http://www.postgresql.org/docs/17/runtime-config-client.html#GUC-ROW-SECURITY[row_security] to on instead, allowing the user to dump the parts of the contents of the table that they have access to.Note that if you use this option currently, you probably also want the dump be in `INSERT` format, as the `COPY FROM` during restore does not support row security. +- `--exclude-extension=*`pattern`*` + + Do not dump any extensions matching *`pattern`*. The pattern is interpreted according to the same rules as for `-e`. `--exclude-extension` can be given more than once to exclude extensions matching any of several patterns. When both `-e` and `--exclude-extension` are given, the behavior is to dump just the extensions that match at least one `-e` switch but no `--exclude-extension` switches. If `--exclude-extension` appears without `-e`, then extensions matching `--exclude-extension` are excluded from what is otherwise a normal dump. + +- `--exclude-table-and-children=*`pattern`*` + + This is the same as the `-T`/`--exclude-table` option, except that it also excludes any partitions or inheritance child tables of the table(s) matching the *`pattern`*. + - `--exclude-table-data=*`pattern`*` Do not dump data for any tables matching *`pattern`*. The pattern is interpreted according to the same rules as for `-t`. `--exclude-table-data` can be given more than once to exclude tables matching any of several patterns. This option is useful when you need the definition of a particular table even though you do not need the data in it.To exclude data for all tables in the database, see `--schema-only`. +- `--exclude-table-data-and-children=*`pattern`*` + + This is the same as the `--exclude-table-data` option, except that it also excludes data of any partitions or inheritance child tables of the table(s) matching the *`pattern`*. + - `--extra-float-digits=*`ndigits`*` Use the specified value of `extra_float_digits` when dumping floating-point data, instead of the maximum available precision. Routine dumps made for backup purposes should not use this option. +- `--filter=*`filename`*` + + Specify a filename from which to read patterns for objects to include or exclude from the dump. The patterns are interpreted according to the same rules as the corresponding options: `-t`/`--table`, `--table-and-children`, `-T`/`--exclude-table`, and `--exclude-table-and-children` for tables, `-n`/`--schema` and `-N`/`--exclude-schema` for schemas, `--include-foreign-data` for data on foreign servers, `--exclude-table-data` and `--exclude-table-data-and-children` for table data, and `-e`/`--extension` and `--exclude-extension` for extensions. To read from `STDIN`, use `-` as the filename. The `--filter` option can be specified in conjunction with the above listed options for including or excluding objects, and can also be specified more than once for multiple filter files. ++ +The file lists one object pattern per row, with the following format: ++ +`{ include | exclude } { extension | foreign_data | table | table_and_children | table_data | table_data_and_children | schema } *PATTERN*` ++ +The first keyword specifies whether the objects matched by the pattern are to be included or excluded. The second keyword specifies the type of object to be filtered using the pattern: `extension` (like `-e`/`--extension` or `--exclude-extension`), `foreign_data` (data on foreign servers, like `--include-foreign-data`; only usable with `include`), `table` (like `-t`/`--table` or `-T`/`--exclude-table`), `table_and_children` (like `--table-and-children` or `--exclude-table-and-children`), `table_data` (like `--exclude-table-data`; only usable with `exclude`), `table_data_and_children` (like `--exclude-table-data-and-children`; only usable with `exclude`), and `schema` (like `-n`/`--schema` or `-N`/`--exclude-schema`). ++ +Lines starting with `#` are considered comments and ignored. Comments can be placed after an object pattern row as well. Blank lines are also ignored. + - `--if-exists` Use conditional commands (i.e., add an `IF EXISTS` clause) when cleaning database objects. This option is not valid unless `--clean` is also specified. @@ -1616,14 +1640,30 @@ The following command-line options control the content and format of the output. Do not dump comments. +- `--no-data` + + Do not dump data. + +- `--no-policies` + + Do not dump row security policies. + - `--no-publications` Do not dump publications. +- `--no-schema` + + Do not dump schema (data definitions). + - `--no-security-labels` Do not dump security labels. +- `--no-statistics` + + Do not dump statistics. This is the default. + - `--no-subscriptions` Do not dump subscriptions. @@ -1632,6 +1672,10 @@ The following command-line options control the content and format of the output. By default, `pg_dump` will wait for all files to be written safely to disk. This option causes `pg_dump` to return without waiting, which is faster, but means that a subsequent operating system crash can leave the dump corrupt. Generally, this option is useful for testing but should not be used when dumping data from production installation. +- `--no-table-access-method` + + Do not output commands to select table access methods. With this option, all objects will be created with whichever table access method is the default during restore. This option is ignored when emitting an archive (non-text) output file. For the archive formats, you can specify the option when you call `pg_restore`. + - `--no-tablespaces` Do not output commands to select tablespaces. With this option, all objects will be created in whichever tablespace is the default during restore.This option is ignored when emitting an archive (non-text) output file. For the archive formats, you can specify the option when you call `pg_restore`. @@ -1652,6 +1696,10 @@ The following command-line options control the content and format of the output. Force quoting of all identifiers. This option is recommended when dumping a database from a server whose IvorySQL major version is different from pg_dump's, or when the output is intended to be loaded into a server of a different major version. By default, pg_dump quotes only identifiers that are reserved words in its own major version. This sometimes results in compatibility issues when dealing with servers of other versions that may have slightly different sets of reserved words. Using `--quote-all-identifiers` prevents such issues, at the price of a harder-to-read dump script. +- `--restrict-key=*`restrict_key`*` + + Use the provided string as the `psql` `\restrict` key in the dump output. This can only be specified for plain-text dumps, i.e., when `--format` is set to `plain` or the `--format` option is omitted. If no restrict key is specified, `pg_dump` will generate a random one as needed. Keys may contain only alphanumeric characters. This option is primarily intended for testing purposes and other scenarios that require repeatable output (e.g., comparing dump files). It is not recommended for general use, as a malicious server with advance knowledge of the key may be able to inject arbitrary code that will be executed on the machine that runs `psql` with the dump output. + - `--rows-per-insert=*`nrows`*` Dump data as `INSERT` commands (rather than `COPY`). Controls the maximum number of rows per `INSERT` command. The value specified must be a number greater than zero. Any error during restoring will cause only rows that are part of the problematic `INSERT` to be lost, rather than the entire table contents. @@ -1660,6 +1708,10 @@ The following command-line options control the content and format of the output. Only dump the named section. The section name can be `pre-data`, `data`, or `post-data`. This option can be specified more than once to select multiple sections. The default is to dump all sections.The data section contains actual table data, large-object contents, and sequence values. Post-data items include definitions of indexes, triggers, rules, and constraints other than validated check constraints. Pre-data items include all other data definition items. +- `--sequence-data` + + Include sequence data in the dump. This is the default behavior except when `--no-data`, `--schema-only`, or `--statistics-only` is specified. + - `--serializable-deferrable` Use a `serializable` transaction for the dump, to ensure that the snapshot used is consistent with later database states; but do this by waiting for a point in the transaction stream at which no anomalies can be present, so that there isn't a risk of the dump failing or causing other transactions to roll back with a `serialization_failure`.This option is not beneficial for a dump which is intended only for disaster recovery. It could be useful for a dump used to load a copy of the database for reporting or other read-only load sharing while the original database continues to be updated. Without it the dump may reflect a state which is not consistent with any serial execution of the transactions eventually committed. For example, if batch processing techniques are used, a batch may show as closed in the dump without all of the items which are in the batch appearing.This option will make no difference if there are no read-write transactions active when pg_dump is started. If read-write transactions are active, the start of the dump may be delayed for an indeterminate length of time. Once running, performance with or without the switch is the same. @@ -1668,10 +1720,26 @@ The following command-line options control the content and format of the output. Use the specified synchronized snapshot when making a dump of the database.This option is useful when needing to synchronize the dump with a logical replication slot or with a concurrent session.In the case of a parallel dump, the snapshot name defined by this option is used rather than taking a new snapshot. +- `--statistics` + + Dump optimizer statistics. + +- `--statistics-only` + + Dump only the statistics, not the schema (data definitions) or data. Optimizer statistics for tables, materialized views, foreign tables, and indexes are dumped. + - `--strict-names` Require that each extension (`-e`/`--extension`), schema (`-n`/`--schema`) and table (`-t`/`--table`) qualifier match at least one extension/schema/table in the database to be dumped. Note that if none of the extension/schema/table qualifiers find matches, pg_dump will generate an error even without `--strict-names`.This option has no effect on `-N`/`--exclude-schema`, `-T`/`--exclude-table`, or `--exclude-table-data`. An exclude pattern failing to match any objects is not considered an error. +- `--sync-method=*`method`*` + + When set to `fsync`, which is the default, `pg_dump --format=directory` will recursively open and synchronize all files in the archive directory. On Linux, `syncfs` may be used instead to ask the operating system to synchronize the whole file system that contains the archive directory. This option has no effect when `--no-sync` is used or `--format` is not set to `directory`. + +- `--table-and-children=*`pattern`*` + + This is the same as the `-t`/`--table` option, except that it also includes any partitions or inheritance child tables of the table(s) matching the *`pattern`*. + - `--use-set-session-authorization` 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. Also, a dump using `SET SESSION AUTHORIZATION` will certainly require superuser privileges to restore correctly, whereas `ALTER OWNER` requires lesser privileges.