Re: May be BUG. Periodic burst growth of the checkpoint_req counter on replica. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: May be BUG. Periodic burst growth of the checkpoint_req counter on replica.
Date
Msg-id ddbc4b52-da56-49b4-b2de-1e28ac49f5f2@oss.nttdata.com
Whole thread Raw
In response to Re: May be BUG. Periodic burst growth of the checkpoint_req counter on replica.  ("Anton A. Melnikov" <a.melnikov@postgrespro.ru>)
List pgsql-hackers

On 2024/09/30 16:00, Anton A. Melnikov wrote:
> 
> On 30.09.2024 06:26, Fujii Masao wrote:
>> Thanks for the review! I've pushed the 0001 patch.
> 
> Thanks a lot!
> 
>>> As for switching in the pg_proc.dat entries the idea was to put them in order
>>> so that the pg_stat_get_checkpointer* functions were grouped together.
>>> I don't know if this is the common and accepted practice. Simply i like it better this way.
>>> Sure, if you think it's unnecessary, let it stay as is with minimal diff.
>>
>> I understand your point, but I didn't made that change to keep the diff minimal,
>> which should make future back-patching easier.
> 
> Agreed. Its quite reasonable. I've not take into account the backporting
> possibility at all. This is of course wrong.
> 
>>> In addition, checkpoints may be skipped due to "checkpoints are occurring
>>> too frequently" error. Not sure, but maybe add this information to
>>> the new description?
>>
>>  From what I can see in the code, that error message doesn’t seem to indicate
>> the checkpoint is being skipped. In fact, checkpoints are still happening
>> actually when that message appears. Am I misunderstanding something?
> 
> No, you are right! This is my oversight. I didn't notice that elevel is just a log
> not a error. Thanks!

Ok, so I pushed 0002.patch. Thanks for the review!

Regards,

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




pgsql-hackers by date:

Previous
From: Aditya Singh
Date:
Subject: Request for Insights on ID Column Migration Approach
Next
From: Tom Lane
Date:
Subject: Re: pg_basebackup and error messages dependent on the order of the arguments