| From: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>, "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
| Subject: | Re: index question |
| Date: | 2016-05-03 01:21:13 |
| Message-ID: | CADp-Sm6qXHbZNsExP68FY7mx2xEV9KqFMK44p0SAnTB9OX_55w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 3 May 2016 08:45 David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> I am not sure, but I think if the size of index is very huge and you
>> suspect they are not being used, you might want to check the bloats
>> percentage in the index. If this is true, perhaps a reindex might help.
>>
>
> If they aren't being used just drop them. Its when they are used and get
> bloated that you are in trouble.
>
Yes you are right. My bad. It is when they are bloated and being used by
planner, the scans will be slower.
>
> There are recipes for bloat calculation out there that are worth
> investigating.
>
>
> David J.
>
> --
--
Best Regards
Sameer Kumar | DB Solution Architect
*ASHNIK PTE. LTD.*
101 Cecil Street, #11-11 Tong Eng Building, Singapore 069 533
T: +65 6438 3504 | M: +65 8110 0350 | www.ashnik.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | drum.lucas@gmail.com | 2016-05-03 04:00:41 | Re: Function PostgreSQL 9.2 |
| Previous Message | David G. Johnston | 2016-05-03 01:08:41 | Re: Function PostgreSQL 9.2 |