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

Commit09c6ac9

Browse files
committed
Dept. of second thoughts: it'd be a good idea to flush buffers
during replay of CREATE DATABASE as well as the first time around.Else it's possible that the copy operation will copy obsolete blocks.We are still a long way from guaranteeing anything about using arecently-written database as a CREATE template, but this seems neededto ensure the existing behavior holds up during replay.
1 parent3afd7ea commit09c6ac9

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

‎src/backend/commands/dbcommands.c

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
*
1010
*
1111
* IDENTIFICATION
12-
* $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.143 2004/08/3002:54:38 momjian Exp $
12+
* $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.144 2004/08/3003:50:24 tgl Exp $
1313
*
1414
*-------------------------------------------------------------------------
1515
*/
@@ -1136,6 +1136,13 @@ dbase_redo(XLogRecPtr lsn, XLogRecord *record)
11361136
dst_path)));
11371137
}
11381138

1139+
/*
1140+
* Force dirty buffers out to disk, to ensure source database is
1141+
* up-to-date for the copy. (We really only need to flush buffers for
1142+
* the source database...)
1143+
*/
1144+
BufferSync(-1,-1);
1145+
11391146
#ifndefWIN32
11401147

11411148
/*

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp