Greg Smith <g...@2ndquadrant.com> writes:
> You're saying to watch out for (3); I think that's not usually the case,
> but that's a fair thing to warn about. Even in that case, though, it
> may still be worth dropping the index. Year-end processes are not
> usually very sensitive to whether they take a little or a long time to
> execute. But you will be paying to maintain the index every day while
> it is there.
Yeah. Another idea worth considering is to have the year-end processing
build the index it wants, use it, drop it. It seems unlikely that it's
worth maintaining an index year-round for such infrequent usage.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
