Re: Issue with pg_stat_subscription_stats - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Issue with pg_stat_subscription_stats
Date
Msg-id 20221006234343.xjobbvnxkwvynxyo@awork3.anarazel.de
Whole thread Raw
In response to Re: Issue with pg_stat_subscription_stats  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Issue with pg_stat_subscription_stats  (Andres Freund <andres@anarazel.de>)
Re: Issue with pg_stat_subscription_stats  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi,

On 2022-10-06 14:10:56 +0900, Michael Paquier wrote:
> On Tue, Jul 12, 2022 at 09:31:16AM +0530, Amit Kapila wrote:
> > I am not against backpatching this but OTOH it doesn't appear critical
> > enough to block one's work, so not backpatching should be fine.
> 
> We are just talking about the reset timestamp not being set at
> when the object is created, right?  This does not strike me as
> critical, so applying it only on HEAD is fine IMO.  A few months ago,
> while in beta, I would have been fine with something applied to
> REL_15_STABLE.  Now that we are in RC, that's not worth taking a risk
> in my opinion.

Agreed.

> Amit or Andres, are you planning to double-check and perhaps merge
> this patch to take care of the inconsistency?

I'll run it through CI and then to master unless somebody pipes up in the
meantime.

Thanks for bringing this thread up, I'd lost track of it.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types
Next
From: Tom Lane
Date:
Subject: Re: Avoid mix char with bool type in comparisons