Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Date: 2022-02-21 11:26:26
Message-ID: YhN24j2ij3S6T9wy@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 21, 2022 at 04:19:59PM +0530, Amit Kapila wrote:
> On Mon, Feb 21, 2022 at 11:21 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>> Agreed.
>>
>
> +1. How about attached?

That's the same thing as what I sent upthread, so that's correct to
me, except that I have fixed both functions :)

You are not touching pg_stat_get_subscription_worker() because the
plan is to revert it from HEAD? I have not followed the other
discussion closely.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-02-21 11:30:43 Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Previous Message Amit Kapila 2022-02-21 10:49:59 Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset