mirror of
https://github.com/postgres/postgres.git
synced 2025-10-25 13:17:41 +03:00
Rename wal_log_hintbits to wal_log_hints, per discussion on pgsql-hackers.
Sawada Masahiko
This commit is contained in:
@@ -189,7 +189,7 @@ extern bool XLogArchiveMode;
|
||||
extern char *XLogArchiveCommand;
|
||||
extern bool EnableHotStandby;
|
||||
extern bool fullPageWrites;
|
||||
extern bool walLogHintbits;
|
||||
extern bool walLogHints;
|
||||
extern bool log_checkpoints;
|
||||
extern int num_xloginsert_slots;
|
||||
|
||||
@@ -219,9 +219,9 @@ extern int wal_level;
|
||||
* we have to protect them against torn page writes. When you only set
|
||||
* individual bits on a page, it's still consistent no matter what combination
|
||||
* of the bits make it to disk, but the checksum wouldn't match. Also WAL-log
|
||||
* them if forced by wal_log_hintbits=on.
|
||||
* them if forced by wal_log_hints=on.
|
||||
*/
|
||||
#define XLogHintBitIsNeeded() (DataChecksumsEnabled() || walLogHintbits)
|
||||
#define XLogHintBitIsNeeded() (DataChecksumsEnabled() || walLogHints)
|
||||
|
||||
/* Do we need to WAL-log information required only for Hot Standby and logical replication? */
|
||||
#define XLogStandbyInfoActive() (wal_level >= WAL_LEVEL_HOT_STANDBY)
|
||||
|
||||
@@ -209,7 +209,7 @@ typedef struct xl_parameter_change
|
||||
int max_prepared_xacts;
|
||||
int max_locks_per_xact;
|
||||
int wal_level;
|
||||
bool wal_log_hintbits;
|
||||
bool wal_log_hints;
|
||||
} xl_parameter_change;
|
||||
|
||||
/* logs restore point */
|
||||
|
||||
Reference in New Issue
Block a user