Re: BUG #17023: wal_log_hints not configured even if it on - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17023: wal_log_hints not configured even if it on
Date
Msg-id YKXHDzCuj+Yi0Cif@paquier.xyz
Whole thread Raw
In response to Re: BUG #17023: wal_log_hints not configured even if it on  (Mohan Nagandlla <nagandllamohan@gmail.com>)
Responses Re: BUG #17023: wal_log_hints not configured even if it on  (Mohan Nagandlla <nagandllamohan@gmail.com>)
List pgsql-bugs
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

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Generated column is not updated (Postgres 13)
Next
From: Mohan Nagandlla
Date:
Subject: Re: BUG #17023: wal_log_hints not configured even if it on