Re: Wait event that should be reported while waiting for WAL archiving to finish

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Atsushi Torikoshi <atorik@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2020-03-24T02:13:44Z
Lists: pgsql-hackers

On 2020/03/23 15:56, Fujii Masao wrote:
> 
> 
> On 2020/03/19 19:39, Atsushi Torikoshi wrote:
>>
>> On Wed, Feb 26, 2020 at 9:19 PM Fujii Masao <masao.fujii@oss.nttdata.com <mailto:masao.fujii@oss.nttdata.com>> wrote:
>>
>>     I have no idea about this. But I wonder how much that change
>>     is helpful to reduce the power consumption because waiting
>>     for WAL archive during the backup basically not so frequently
>>     happens.
>>
>>
>> +1.
>> And as far as I reviewed the patch,  I didn't find any problems.
> 
> Thanks for the review!
> Barring any objection, I will commit this patch.

Pushed! Thanks!

Regards,

-- 
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters



Commits

  1. Add wait events for WAL archive and recovery pause.

  2. Add description about GSSOpenServer wait event into document.

  3. Add description about LogicalRewriteTruncate wait event into document.

  4. GSSAPI encryption support

  5. Create and use wait events for read, write, and fsync operations.