Re: Is there a way to know write statistics on an individual index

From: higherone <higherone(at)gmail(dot)com>
To: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Is there a way to know write statistics on an individual index
Date: 2022-12-13 08:28:40
Message-ID: CAPgEv8fhh-knJOSACN8G=ngWKkHSh-Eg0CS5RX-ZbxJ87tTSPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

It's not a partial index, but I believe the pg_stat_user_tables contains
all the writes on the table, which not necessarily updates the individual
index I'm interested in (e.g. when the updated column is not part of the
index columns) .

On Fri, Dec 9, 2022 at 2:06 PM Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> wrote:

> On Thu, Dec 8, 2022 at 2:53 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> >
> > On Thu, 8 Dec 2022 at 19:59, higherone <higherone(at)gmail(dot)com> wrote:
> > > I know there's a pg_stats_user_indexes that gives statistics about the
> index scans/fetches, but I don't find any information about how many
> writes(insert/update/delete) happen on this individual index.
> > > Is there some tool that could achieve this?
> >
> > Is this a partial index? If not, those should just increase at the
> > same rate that's mentioned in pg_stat_user_tables for the table that
> > the index belongs to.
>
> Well, not deletes, right? And HOT updates won't affect indexes either,
> so they should be subtracted from n_tup_upd.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message vignesh C 2022-12-13 09:17:32 Re: Support logical replication of DDLs
Previous Message li jie 2022-12-13 02:37:15 Re: Support logical replication of DDLs