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 CAA4eK1LezjxzV3yU6ZNTy5GoQR0QbYWen1bQa8uT37OEyM0Jnw@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  (Masahiko Sawada <sawada.mshk@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 Mon, Feb 21, 2022 at 11:21 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> >
> > I am aware about the discussions on the parent view for the first
> > case and its design issues, but it does not change the fact that we'd
> > better address the second case on HEAD IMO.
> >
> > Thoughts?
>
> Agreed.
>

+1. How about attached?

-- 
With Regards,
Amit Kapila.

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgcrypto: Remove internal padding implementation
Next
From: Michael Paquier
Date:
Subject: Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset