Re: BUG #17023: wal_log_hints not configured even if it on

This is the pg_controldata on both

On current master

pg_control version number: 1300
Catalog version number: 202007201
Database system identifier: 6963982442470461472
Database cluster state: in production
pg_control last modified: Thu May 20 02:04:33 2021
Latest checkpoint location: 0/C000110
Latest checkpoint's REDO location: 0/C0000D8
Latest checkpoint's REDO WAL file: 00000002000000000000000C
Latest checkpoint's TimeLineID: 2
Latest checkpoint's PrevTimeLineID: 2
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID: 0:505
Latest checkpoint's NextOID: 24584
Latest checkpoint's NextMultiXactId: 1
Latest checkpoint's NextMultiOffset: 0
Latest checkpoint's oldestXID: 477
Latest checkpoint's oldestXID's DB: 1
Latest checkpoint's oldestActiveXID: 505
Latest checkpoint's oldestMultiXid: 1
Latest checkpoint's oldestMulti's DB: 1
Latest checkpoint's oldestCommitTsXid:0
Latest checkpoint's newestCommitTsXid:0
Time of latest checkpoint: Thu May 20 02:04:33 2021
Fake LSN counter for unlogged rels: 0/3E8
Minimum recovery ending location: 0/0
Min recovery ending loc's timeline: 0
Backup start location: 0/0
Backup end location: 0/0
End-of-backup record required: no
wal_level setting: replica
wal_log_hints setting: on
max_connections setting: 100
max_worker_processes setting: 8
max_wal_senders setting: 10
max_prepared_xacts setting: 0
max_locks_per_xact setting: 64
track_commit_timestamp setting: off
Maximum data alignment: 8
Database block size: 8192
Blocks per segment of large relation: 131072
WAL block size: 8192
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 1996
Size of a large-object chunk: 2048
Date/time type storage: 64-bit integers
Float8 argument passing: by value
Data page checksum version: 0
Mock authentication nonce:
a6265e4a2c8ebb6ecaa69ef02b9a927c4e6dd2a8066f19068e541fd6d9dabef8

On slave

Time of latest checkpoint: Wed May 19 12:59:24 2021
Fake LSN counter for unlogged rels: 0/3E8
Minimum recovery ending location: 0/801AC68
Min recovery ending loc's timeline: 2
Backup start location: 0/5000060
Backup end location: 0/801AC68
End-of-backup record required: no
wal_level setting: replica
wal_log_hints setting: on
max_connections setting: 100
max_worker_processes setting: 8
max_wal_senders setting: 10
max_prepared_xacts setting: 0
max_locks_per_xact setting: 64
track_commit_timestamp setting: off
Maximum data alignment: 8
Database block size: 8192
Blocks per segment of large relation: 131072
WAL block size: 8192
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 1996
Size of a large-object chunk: 2048
Date/time type storage: 64-bit integers
Float8 argument passing: by value
Data page checksum version: 0
Mock authentication nonce:
a6265e4a2c8ebb6ecaa69ef02b9a927c4e6dd2a8066f19068e541fd6d9dabef8

On Thu, 20 May, 2021, 7:49 am Michael Paquier, <michael(at)paquier(dot)xyz> wrote:

> On Thu, May 20, 2021 at 07:13:26AM +0530, Mohan Nagandlla wrote:
> > Now coming to the manual fail over case I have converted the slave as
> > master by using promote_trigger_file it was done successfully. The slave
> is
> > accepting the read and write also. And now I am coverting the old master
> as
> > slave for that I have done everything in new master and now by using
> > pg_rewind I am syncing the data time lines but that command is giving the
> > error like wal_log_hints should be in on . But I have enabled this option
> > from beginning onwards still it is in on but in target server and source
> > server.
>
> What does pg_controldata tell you when run on both clusters? That's
> what pg_rewind looks after in its sanity checks.
> --
> Michael
>