| 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 02:18:55 |
| Message-ID: | YKXHDzCuj+Yi0Cif@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mohan Nagandlla | 2021-05-20 02:25:45 | Re: BUG #17023: wal_log_hints not configured even if it on |
| Previous Message | Tom Lane | 2021-05-20 01:55:48 | Re: Generated column is not updated (Postgres 13) |