Re: Understanding pg_stat_user_indexes - Mailing list pgsql-general

From Josh Kupershmidt
Subject Re: Understanding pg_stat_user_indexes
Date
Msg-id 4ec1cf761002051518j6df2a108xa7d1066d59f1e907@mail.gmail.com
Whole thread Raw
In response to Understanding pg_stat_user_indexes  (Steve Crawford <scrawford@pinpointresearch.com>)
Responses Re: Understanding pg_stat_user_indexes  (Steve Crawford <scrawford@pinpointresearch.com>)
List pgsql-general
On Fri, Feb 5, 2010 at 12:02 PM, Steve Crawford <scrawford@pinpointresearch.com> wrote:
What causes an increment to idx_scan in pg_stat_user_indexes? "Select" queries only? When used to enforce column uniqueness? When used for foreign-key constraints?


The docs are a little sparse here:

http://developer.postgresql.org/pgdocs/postgres/monitoring-stats.html

but I'm assuming that counter gets incremented every time there's an index scan using the index in question, which could occur with SELECT, UPDATE, DELETE, etc. queries which make use of this index. See this thread for related questions and answers, and the note about bitmap index scans:
http://archives.postgresql.org/pgsql-admin/2006-01/msg00319.php
 
I see lots of indexes with an idx_scan-count of zero but which are not actually superfluous as they are required to enforce constraints.

Ultimately, I'm trying to come up with a better way to search for truly useless indexes.


Josh

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: \dt+ sizes don't include TOAST data
Next
From: Andre Lopes
Date:
Subject: How can I test my web application against SQL Injections?