Re: Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: tim_wilson <tim(dot)wilson(at)telogis(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0
Date: 2014-06-06 02:02:01
Message-ID: 32562.1402020121@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

tim_wilson <tim(dot)wilson(at)telogis(dot)com> writes:
> Thanks for you response Tom:
> but what does index_scans:0 mean? vs index scans: 1?

I believe the former means that VACUUM found no removable tuples, so it
had no need to make any passes over the table's indexes.

(Ordinarily you wouldn't see the number of scans as more than 1, unless
VACUUM removed quite a lot of dead tuples, more than it could remember
within maintenance_work_mem; in which case it would make multiple passes
over the indexes to remove index entries.)

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message tim_wilson 2014-06-06 06:43:32 Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0
Previous Message tim_wilson 2014-06-06 00:55:19 Re: autovacuum vacuum creates bad statistics for planner when it log index scans: 0