RE: Failed transaction statistics to measure the logical replication progress
От | osumi.takamichi@fujitsu.com |
---|---|
Тема | RE: Failed transaction statistics to measure the logical replication progress |
Дата | |
Msg-id | TYCPR01MB83730827F456869CFD43460AED1D9@TYCPR01MB8373.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Failed transaction statistics to measure the logical replication progress (Masahiko Sawada <sawada.mshk@gmail.com>) |
Список | pgsql-hackers |
Hi On Friday, March 25, 2022 2:36 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > On Thu, Mar 24, 2022 at 12:30 PM Amit Kapila <amit.kapila16@gmail.com> > wrote: > > > > On Thu, Mar 3, 2022 at 8:58 AM osumi.takamichi@fujitsu.com > > <osumi.takamichi@fujitsu.com> wrote: > > > > > > > This patch introduces two new subscription statistics columns > > (apply_commit_count and apply_rollback_count) to the > > pg_stat_subscription_stats view for counting cumulative transactions > > commits/rollbacks for a particular subscription. Now, users can > > already see the total number of xacts committed/rolled back in a > > particular database via pg_stat_database, so this can be considered > > duplicate information. > > Right. ... > > I am not sure if it is worth adding this additional information or how > > useful it will be for users. Does anyone else want to weigh in on > > this? > > > > If nobody else sees value in this then I feel it is better to mark > > this patch as Returned with feedback or Rejected. We can come back to > > it later if we see more demand for this. > > Marking as Returned with feedback makes sense to me. OK. Thank you so much for sharing your opinions, Sawada-san and Amit-san. I changed the status of this entry to "Returned with feedback" accordingly. Best Regards, Takamichi Osumi
В списке pgsql-hackers по дате отправления: