mirror of
https://github.com/postgres/postgres.git
synced 2025-08-24 09:27:52 +03:00
Improve the checkpoint signaling mechanism so that the bgwriter can tell
the difference between checkpoints forced due to WAL segment consumption and checkpoints forced for other reasons (such as CREATE DATABASE). Avoid generating 'checkpoints are occurring too frequently' messages when the checkpoint wasn't caused by WAL segment consumption. Per gripe from Chris K-L.
This commit is contained in:
@@ -15,7 +15,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.163 2005/06/29 20:34:13 tgl Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.164 2005/06/30 00:00:50 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@@ -542,7 +542,7 @@ createdb(const CreatedbStmt *stmt)
|
||||
* Perhaps if we ever implement CREATE DATABASE in a less cheesy
|
||||
* way, we can avoid this.
|
||||
*/
|
||||
RequestCheckpoint(true);
|
||||
RequestCheckpoint(true, false);
|
||||
|
||||
/*
|
||||
* Set flag to update flat database file at commit.
|
||||
@@ -668,7 +668,7 @@ dropdb(const char *dbname)
|
||||
* open files, which would cause rmdir() to fail.
|
||||
*/
|
||||
#ifdef WIN32
|
||||
RequestCheckpoint(true);
|
||||
RequestCheckpoint(true, false);
|
||||
#endif
|
||||
|
||||
/*
|
||||
|
Reference in New Issue
Block a user