| From: | "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca> |
|---|---|
| To: | "Fujii Masao" <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "Sergei Kornilov" <sk(at)zsrv(dot)org>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: recovery_target_action=pause with confusing hint |
| Date: | 2020-04-08 07:41:40 |
| Message-ID: | 2020040815413793983317@highgo.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> we should notice it in document I think.
>There is the following explation about the relationship the recovery
>pause and the promotion, in the document. You may want to add more
>descriptions into the docs?
>------------------------------
>If a promotion is triggered while recovery is paused, the paused
>state ends and a promotion continues.
>------------------------------
For example we can add this words:
First-time pg_wal_replay_pause() called during recovery which triggered
as promotion, pg_wal_replay_pause() show success but it did not really
pause the recovery.
Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-04-08 07:46:05 | Re: [HACKERS] Restricting maximum keep segments by repslots |
| Previous Message | Kuntal Ghosh | 2020-04-08 07:30:14 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |