Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0 - Mailing list pgsql-performance

From tim_wilson
Subject Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0
Date
Msg-id 1402016119875-5806283.post@n5.nabble.com
Whole thread Raw
In response to Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0  (tim_wilson <tim.wilson@telogis.com>)
List pgsql-performance
Thanks for you response Tom:
but what does index_scans:0 mean? vs index scans: 1?

I have had a look at the c code but cannot see when it that would be the
case.



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/autovacuum-vacuum-creates-bad-statistics-for-planner-when-it-log-index-scans-0-tp5804416p5806283.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.


pgsql-performance by date:

Previous
From: Vincent Lasmarias
Date:
Subject: Re: CPU load spikes when CentOS tries to reclaim 'cached' memory
Next
From: Tom Lane
Date:
Subject: Re: Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0