Re: Fix typo in procarrary.c - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Fix typo in procarrary.c
Date
Msg-id ec39f0dd-eaa8-d41d-182b-765037637568@oss.nttdata.com
Whole thread Raw
In response to Re: Fix typo in procarrary.c  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: Fix typo in procarrary.c
List pgsql-hackers

On 2020/08/21 12:29, Masahiko Sawada wrote:
> On Fri, 21 Aug 2020 at 11:18, Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>>
>>
>>
>> On 2020/08/21 10:58, Masahiko Sawada wrote:
>>> Hi,
>>>
>>> I've attached the patch for $subject.
>>>
>>> s/replications lots/replication slots/
>>
>> Thanks for the patch!
>>
>> Also it's better to s/replications slots/replication slots/ ?
>>
>> --- a/src/backend/storage/ipc/procarray.c
>> +++ b/src/backend/storage/ipc/procarray.c
>> @@ -198,7 +198,7 @@ typedef struct ComputeXidHorizonsResult
>>            * be removed.
>>            *
>>            * This likely should only be needed to determine whether pg_subtrans can
>> -        * be truncated. It currently includes the effects of replications slots,
>> +        * be truncated. It currently includes the effects of replication slots,
>>            * for historical reasons. But that could likely be changed.
>>            */
>>           TransactionId oldest_considered_running;
>>
> 
> Indeed. I agree with you.

Thanks! So I pushed both fixes.

Regards,

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



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Fix typo in procarrary.c
Next
From: Amit Kapila
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions