Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, 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 10:49:59
Message-ID: CAA4eK1LezjxzV3yU6ZNTy5GoQR0QbYWen1bQa8uT37OEyM0Jnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 21, 2022 at 11:21 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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 Content-Type Size
fix_pgproc_get_repl_slot_1.patch application/octet-stream 1.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-02-21 11:26:26 Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Previous Message Peter Eisentraut 2022-02-21 10:42:07 Re: pgcrypto: Remove internal padding implementation