Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Date
Msg-id CAA4eK1LLsxOXaPaP52MkQ4fREV=wE9nQrM5C5ZZhZWnhrAQqYg@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, Feb 25, 2022 at 8:57 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Thu, Feb 24, 2022 at 12:03 PM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Wed, Feb 23, 2022 at 09:52:02AM +0530, Amit Kapila wrote:
> > > Thanks, so you are okay with me pushing that patch just to HEAD.
> >
> > Yes, I am fine with that.  I am wondering about patching the second
> > function though, to avoid any risk of forgetting it, but I am fine to
> > leave that to your judgement.
> >
>
> The corresponding patch with other changes is not very far from being
> ready to commit. So, will do it along with that.
>

This is done as part of commit:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7a85073290856554416353a89799a4c04d09b74b


-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: "wangw.fnst@fujitsu.com"
Date:
Subject: RE: Logical replication timeout problem
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Make mesage at end-of-recovery less scary.