From: | movead li <movead(dot)li(at)highgo(dot)ca> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Cc: | Sergei Kornilov <sk(at)zsrv(dot)org> |
Subject: | Re: recovery_target_action=pause with confusing hint |
Date: | 2020-03-31 08:48:44 |
Message-ID: | 158564452423.791.15893021658342964840.pgcf@coridan.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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().
#####################################
postgres=# select pg_wal_replay_pause();
pg_wal_replay_pause
---------------------
(1 row)
postgres=# select pg_wal_replay_pause();
ERROR: standby promotion is ongoing
HINT: pg_wal_replay_pause() cannot be executed after promotion is triggered.
postgres=# select pg_wal_replay_pause();
ERROR: recovery is not in progress
HINT: Recovery control functions can only be executed during recovery.
postgres=#
##############################################################
The new status of this patch is: Waiting on Author
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-03-31 09:09:04 | Re: WAL usage calculation patch |
Previous Message | Artur Zakirov | 2020-03-31 08:34:18 | Re: truncating timestamps on arbitrary intervals |