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

Commit19d1275

Browse files
committed
Add comment about checkpoint panic behavior during shutdown, per
suggestion from Qingqing Zhou.
1 parentb1faf36 commit19d1275

File tree

1 file changed

+5
-2
lines changed
  • src/backend/access/transam

1 file changed

+5
-2
lines changed

‎src/backend/access/transam/xlog.c

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
* Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group
88
* Portions Copyright (c) 1994, Regents of the University of California
99
*
10-
* $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.187 2005/04/17 03:04:29 momjian Exp $
10+
* $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.188 2005/04/23 18:49:54 tgl Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -4925,7 +4925,10 @@ CreateCheckPoint(bool shutdown, bool force)
49254925
*
49264926
* This I/O could fail for various reasons. If so, we will fail to
49274927
* complete the checkpoint, but there is no reason to force a system
4928-
* panic. Accordingly, exit critical section while doing it.
4928+
* panic. Accordingly, exit critical section while doing it. (If
4929+
* we are doing a shutdown checkpoint, we probably *should* panic ---
4930+
* but that will happen anyway because we'll still be inside the
4931+
* critical section established by ShutdownXLOG.)
49294932
*/
49304933
END_CRIT_SECTION();
49314934

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp