pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: since when has pg_stat_user_indexes.idx_scan been counting?
Date: Thu, 12 May 2011 16:16:18 -0400
Message-ID: <8490.1305231378@sss.pgh.pa.us> (raw)
In-Reply-To: <4DCC3DD9.4000402@2ndquadrant.com>
References: <BANLkTikhNLPhCjE819=RFG-+CB6UV4GbUA@mail.gmail.com>
	<4DCC24BD.9040900@fuzzy.cz>
	<4DCC3DD9.4000402@2ndquadrant.com>

Greg Smith <greg@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



view thread (10+ messages)  latest in thread

Message-ID: <8490.1305231378@sss.pgh.pa.us>
Permalink:  ../8490.1305231378@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8490.1305231378@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, greg@2ndquadrant.com, tv@fuzzy.cz
  Subject: Re: since when has pg_stat_user_indexes.idx_scan been counting?
  In-Reply-To: <8490.1305231378@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox