Re: Change log level for notifying hot standby is waiting non-overflowed snapshot - Mailing list pgsql-hackers

From torikoshia
Subject Re: Change log level for notifying hot standby is waiting non-overflowed snapshot
Date
Msg-id 21bd91ba632219282627c02927988682@oss.nttdata.com
Whole thread Raw
In response to Re: Change log level for notifying hot standby is waiting non-overflowed snapshot  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Change log level for notifying hot standby is waiting non-overflowed snapshot
List pgsql-hackers
On 2025-03-24 00:08, Fujii Masao wrote:

>> 
>> Do you also think the errhint message is unnecessary?
>> I agree with your idea to add a description of the overflowed 
>> subtransaction in the manual, but I'm not sure all users will be able 
>> to find it.
>> Some people may not understand what needs to be done to make the 
>> snapshot ready for hot standby.
>> I think adding an errhint may help those users.
> 
> I see your concern that users might overlook the documentation and
> struggle to find a solution. However, I still believe it's better to
> include this information in the documentation rather than logging it
> as a hint. Since the scenario where the hint would be useful is
> relatively rare, logging it every time might be more confusing than 
> helpful.

Thanks for your opinion and it sounds reasonable.

Attached an updated patch.

-- 
Regards,

--
Atsushi Torikoshi
Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.
Attachment

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Add Postgres module info
Next
From: Robert Haas
Date:
Subject: Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints