| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
| Cc: | dennisr(at)visi(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: help interpreting pg_stat_user_index view values |
| Date: | 2014-01-05 22:21:42 |
| Message-ID: | CAL_0b1vW6U3BRf19wJfuj9_KEdoTp1J6wY7WPUV6cmvBdBk-RA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jan 5, 2014 at 2:19 PM, Gavin Flower
<GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
> On 06/01/14 11:08, Sergey Konoplev wrote:
> [...]
>
>> An index might be considered as useless when there were no idx scans for
>> the significantly long period. However it might be non-trivial to define
>> this period. Eg. one have a query building an annual report that uses this
>> index and the period here is one year.
>
> [...]
>
> An index only used by an annual report, should possibly be only created
> prior to the report run & dropped immediately afterwards - why carry its
> overhead for the bulk of the year?
I fully agree. This is the matter of implementation.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Darling | 2014-01-05 22:34:37 | Re: help interpreting pg_stat_user_index view values |
| Previous Message | Gavin Flower | 2014-01-05 22:19:33 | Re: help interpreting pg_stat_user_index view values |