Re: Add Information during standby recovery conflicts - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Add Information during standby recovery conflicts
Date
Msg-id 665ebdf3-d517-18c6-6b32-06fcdd9d6f83@oss.nttdata.com
Whole thread Raw
In response to Re: Add Information during standby recovery conflicts  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Add Information during standby recovery conflicts  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
List pgsql-hackers

On 2021/01/08 11:17, Kyotaro Horiguchi wrote:
> At Fri, 8 Jan 2021 01:32:11 +0900, Fujii Masao <masao.fujii@oss.nttdata.com> wrote in
>>
>> Attached is the updated version of the patch. This can be applied to
>> current master.
>>
>> With the patch, for example, if the startup process waited longer than
>> deadlock_timeout for the recovery conflict on the lock, the latter log
>> message in the followings would be additionally output.
>>
>>      LOG: recovery still waiting after 1001.223 ms: recovery conflict on
>>      lock
>>      LOG: recovery finished waiting after 19004.694 ms: recovery conflict
>>      on lock
> 
> +            /*
> +             * Emit the log message if recovery conflict on buffer pin was resolved but
> +             * the startup process waited longer than deadlock_timeout for it.
> 
> The first line is beyond the 80th column.

Thanks for pointing out this! This happened because I forgot to run pgindent
for bufmgr.c. Attached is the updated version of the patch.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment

pgsql-hackers by date:

Previous
From: Josef Šimánek
Date:
Subject: Re: [PATCH] Simple progress reporting for COPY command
Next
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit