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

Yes but the wal_log_hints will be in on from the begining of the server.
Which means it is in on when I am starting the server.

On Wed, 19 May, 2021, 9:21 pm Mohan Nagandlla, <nagandllamohan(at)gmail(dot)com>
wrote:

> Yes but the wal_log_hints will be in on from the begining if the server.
>
> On Wed, 19 May, 2021, 8:12 pm Bruce Momjian, <bruce(at)momjian(dot)us> wrote:
>
>> On Wed, May 19, 2021 at 09:33:57AM +0000, PG Bug reporting form wrote:
>> > The following bug has been logged on the website:
>> >
>> > Bug reference: 17023
>> > Logged by: Mohan nagandlla
>> > Email address: nagandllamohan(at)gmail(dot)com
>> > PostgreSQL version: 13.2
>> > Operating system: Alpine
>> > Description:
>> >
>> > Hi team,
>> > I am doing streaming replication and everything is going good but at
>> fail
>> > over case while coversion of old master to slave I am using pg_rewind
>> it is
>> > showing error like wal_log_hints is in on but I have enabled that and
>> > restart the server also if I do it on 10 times 3 times it's passing 7
>> times
>> > it's failing may I know what am I missing?
>>
>> I think you have to have had wal_log_hints for the entire time that WAL
>> was generated for your rewind timespan. Does that help?
>>
>> --
>> Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
>> EDB https://enterprisedb.com
>>
>> If only the physical world exists, free will is an illusion.
>>
>>