| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add Information during standby recovery conflicts |
| Date: | 2020-11-30 17:59:15 |
| Message-ID: | 526ff0bc-612d-9083-5564-56e8219c1b8b@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/11/20 18:17, Drouvot, Bertrand wrote:
> Hi,
>
> On 11/17/20 4:44 PM, Fujii Masao wrote:
>>
>> Thanks for updating the patch! Here are review comments.
>>
>> + Controls whether a log message is produced when the startup process
>> + is waiting longer than <varname>deadlock_timeout</varname>
>> + for recovery conflicts.
>>
>> But a log message can be produced also when the backend is waiting
>> for recovery conflict. Right? If yes, this description needs to be corrected.
>
> Thanks for looking at it!
>
> I don't think so, only the startup process should write those new log messages.
>
> What makes you think that would not be the case?
Probably my mis-underding of the patch did that. Sorry for noise..
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-11-30 18:04:07 | Re: Add Information during standby recovery conflicts |
| Previous Message | Alvaro Herrera | 2020-11-30 17:57:09 | Re: Autovacuum on partitioned table (autoanalyze) |