|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Cc:||Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Issue with pg_stat_subscription_stats|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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.
> 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
Thanks for bringing this thread up, I'd lost track of it.
|Next Message||Tom Lane||2022-10-06 23:52:53||Re: Avoid mix char with bool type in comparisons|
|Previous Message||Tom Lane||2022-10-06 23:35:27||Re: Reducing the chunk header sizes on all memory context types|