Re: Design of pg_stat_subscription_workers vs pgstats

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Design of pg_stat_subscription_workers vs pgstats
Date: 2022-02-03 04:48:28
Message-ID: CAKFQuwba8iE+vp3EqXXihtNASomo9b-MnUjHHrG5R95sqQ2qGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, February 2, 2022, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
wrote:

> and have other error
> information in pg_stat_subscription_workers view.
>

What benefit is there to keeping the existing collector-based
pg_stat_subscripiton_workers view? If we re-write it using shmem IPC then
we might as well put everything there and forego using a catalog. Then it
behaves in a similar manner to pg_stat_activity but for logical replication
workers.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-02-03 04:58:53 Re: 2022-01 Commitfest
Previous Message Julien Rouhaud 2022-02-03 04:46:26 Re: support for CREATE MODULE