Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit2097723

Browse files
committed
Remove pg_restore's --single-transaction option, as it throws errors in
certain cases.
1 parent02aea36 commit2097723

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎contrib/pg_upgrade/pg_upgrade.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -309,11 +309,12 @@ create_new_objects(void)
309309

310310
/*
311311
*Using pg_restore --single-transaction is faster than other
312-
*methods, like --jobs. pg_dump only produces its output at the
312+
*methods, like --jobs. However, --single-transaction throws
313+
*an error. pg_dump only produces its output at the
313314
*end, so there is little parallelism using the pipe.
314315
*/
315316
exec_prog(RESTORE_LOG_FILE,NULL, true,
316-
"\"%s/pg_restore\" %s --exit-on-error --single-transaction --verbose --dbname \"%s\" \"%s\"",
317+
"\"%s/pg_restore\" %s --exit-on-error --verbose --dbname \"%s\" \"%s\"",
317318
new_cluster.bindir,cluster_conn_opts(&new_cluster),
318319
old_db->db_name,file_name);
319320
}

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp