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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Mohan Nagandlla <nagandllamohan(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17023: wal_log_hints not configured even if it on
Date: 2021-05-20 00:15:48
Message-ID: YKWqND+dAfaxvgjk@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 19, 2021 at 09:22:45PM +0530, Mohan Nagandlla wrote:
> 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.

Please describe more precisely the flow of what you are doing here.
It looks like what you are missing is that wal_log_hints needs to be
enabled on the target server, not the source. Please note that this
needs to be reflected in the control file of the target cluster (fetch
for "wal_log_hints setting" in the output generated by
pg_controldata).
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2021-05-20 01:02:39 Re: Generated column is not updated (Postgres 13)
Previous Message Devrim Gündüz 2021-05-19 23:21:44 Re: BUG #17016: Cannot sync pgdg-common repo with reposync due to failed signature check