Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CN/modules/ROOT/pages/9.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2573,6 +2573,12 @@ pg_restore接受下列命令行参数。

要求每一个模式( `-n` / `--schema`)以及表( `-t` / `--table`)限定词匹配备份文件中至少一个模式/表。

- `--transaction-size=N`

以一系列事务的方式执行恢复,每个事务最多处理 `N` 个数据库对象。`N` 必须是一个正整数。此选项隐含了 `--exit-on-error`,且不能与 `-1` / `--single-transaction` 同时使用。请注意,并行工作连接(`-j` / `--jobs`)不使用此批量大小;它们会在每条命令后提交,以便结果对其他工作进程立即可见。

`--transaction-size` 提供了介于默认行为(每条 SQL 命令一个事务)和 `-1` / `--single-transaction`(所有恢复对象共用一个事务)之间的折中选择。虽然 `--single-transaction` 开销最小,但对于大型数据库可能并不实用,因为该事务会对每个恢复的对象加锁,从而可能耗尽服务器的锁表空间。将 `--transaction-size` 设置为几千个对象,既能获得几乎相同的性能收益,又能限制所需的锁表空间大小。

- `--use-set-session-authorization`

输出 SQL 标准的 `SET SESSION AUTHORIZATION` 命令取代 `ALTER OWNER` 命令来决定对象拥有权。这会让转储更加兼容标准,但是依赖于转储中对象的历史,可能无法正确恢复。
Expand Down
6 changes: 6 additions & 0 deletions EN/modules/ROOT/pages/9.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2547,6 +2547,12 @@ Only restore the named section. The section name can be `pre-data`, `data`, or `

Require that each schema (`-n`/`--schema`) and table (`-t`/`--table`) qualifier match at least one schema/table in the backup file.

- `--transaction-size=N`

Execute the restore as a series of transactions, each processing up to `N` database objects. `N` must be a positive integer. This option implies `--exit-on-error`, and cannot be combined with `-1` / `--single-transaction`. Note that parallel worker connections (`-j` / `--jobs`) do not use this batch size; they commit after each command so that results are immediately visible to other workers.

`--transaction-size` offers an intermediate choice between the default behavior (one transaction per SQL command) and `-1` / `--single-transaction` (one transaction for all restored objects). While `--single-transaction` has the least overhead, it may be impractical for large databases because the transaction takes a lock on each restored object, possibly exhausting the server's lock table space. Using `--transaction-size` with a size of a few thousand objects offers nearly the same performance benefits while capping the amount of lock table space needed.

- `--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.
Expand Down
Loading