Re: Change log level for notifying hot standby is waiting non-overflowed snapshot

From: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change log level for notifying hot standby is waiting non-overflowed snapshot
Date: 2025-03-04 01:01:32
Message-ID: 5bfb5f14b2211e052ce856f9d39e7cb6@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-03-04 03:17, Fujii Masao wrote:

>> Agreed and I feel that a message suggesting something like "check if
>> there are any overflowing transactions on the primary side" would make
>> it useful.
>
> I’m wondering if this message might still be confusing for users.
> Would they immediately understand what "overflowing transactions"
> means?
> Even after reading this message, it seems also unclear what actions
> they should take to resolve the issue. Plus, this message can appear
> multiple times if there are multiple overflowing transactions before
> starting accepting read-only connections - which could be even more
> confusing.

It seems better to reconsider the content and timing of this message
output.

I personally think that logging information about this situation where
subtransaction overflowed and it prevents hot standby connections would
be helpful for users and support providers to understand the cause of
the issue.
Do you think such logging is unnecessary?

--
Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-03-04 01:21:18 Next commitfest app release is planned for March 18th
Previous Message Michael Paquier 2025-03-04 00:56:55 Re: Add Pipelining support in psql