| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com> |
| Cc: | Abdul Sayeed <abdulsayeed24(at)gmail(dot)com>, Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>, pgsql-general general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to find out unused indexes? |
| Date: | 2013-09-03 16:24:38 |
| Message-ID: | CAMkU=1wc8H_EjS-wTCaGQWgfVHdZrH-oLntyra77M56-EdR00g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 3, 2013 at 8:48 AM, ascot(dot)moss(at)gmail(dot)com
<ascot(dot)moss(at)gmail(dot)com> wrote:
> Thanks.
>
> how about the case as follows?
>
> idx_scan = 0 and idx_tup_read = 0 and idx_tup_fetch = 0, but
> idx_blks_read is not 0 and idx_blks_hit is not 0
> ?
Maintaining an unused index still requires its blocks to be read.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Janek Sendrowski | 2013-09-03 19:10:48 | Re: store multiple rows with the SELECT INTO statement |
| Previous Message | Kevin Grittner | 2013-09-03 16:23:40 | Re: store multiple rows with the SELECT INTO statement |