Re: Wait event that should be reported while waiting for WALarchiving to finish - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Wait event that should be reported while waiting for WALarchiving to finish
Date
Msg-id 78b1f221-b946-4977-611c-e96963925168@oss.nttdata.com
Whole thread Raw
In response to Re: Wait event that should be reported while waiting for WALarchiving to finish  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers

On 2020/02/14 15:45, Michael Paquier wrote:
> On Fri, Feb 14, 2020 at 12:47:19PM +0900, Fujii Masao wrote:
>> logical_rewrite_truncate_v1.patch adds the description of
>> LogicalRewriteTruncate into the doc. This needs to be
>> back-patched to v10 where commit 249cf070e3 introduced
>> LogicalRewriteTruncate event.
> 
> Indeed.  You just be careful about the number of fields for morerows,
> as that's not the same across branches.
> 
>> gss_open_server_v1.patch adds the description of GSSOpenServer
>> into the doc and update the code in pgstat_get_wait_client().
>> This needs to be applied in v12 where commit b0b39f72b9 introduced
>> GSSOpenServer event.
>>
>> gss_open_server_for_master_v1.patch does not only what the above
>> patch does but also update wait event enum into alphabetical order.
>> This needs to be applied in the master.
> 
> Thanks for splitting things.  All that looks correct to me.

Thanks for the review! Pushed the patches for
LogicalRewriteTruncate and GSSOpenServer.

Regards,

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



pgsql-hackers by date:

Previous
From: Takashi Menjo
Date:
Subject: RE: [PoC] Non-volatile WAL buffer
Next
From: Fujii Masao
Date:
Subject: Re: Wait event that should be reported while waiting for WALarchiving to finish