Re: recovery_target_action=pause with confusing hint - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: recovery_target_action=pause with confusing hint
Date
Msg-id 6993181585648248@iva6-161d47f95e63.qloud-c.yandex.net
Whole thread Raw
In response to Re: recovery_target_action=pause with confusing hint  (movead li <movead.li@highgo.ca>)
Responses Re: recovery_target_action=pause with confusing hint  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Hello

> When I test the patch, I find an issue: I start a stream with 'promote_trigger_file'
> GUC valid, and exec pg_wal_replay_pause() during recovery and as below it
> shows success to pause at the first time. I think it use a initialize
> 'SharedPromoteIsTriggered' value first time I exec the pg_wal_replay_pause().

hm. Are you sure this is related to this patch? Could you explain the exact timing? I mean log_statement = all and
relevantlogs.
 
Most likely this is expected change by
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=496ee647ecd2917369ffcf1eaa0b2cdca07c8730

My proposal does not change the behavior after this commit, only changing the lines in the logs.

regards, Sergei



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: WAL usage calculation patch
Next
From: Amit Kapila
Date:
Subject: Re: WAL usage calculation patch