Re: explanation for seeks in VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: explanation for seeks in VACUUM
Date: 2007-12-15 00:04:50
Message-ID: 15476.1197677090@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> Where am I going wrong? Are many of these lseeks no-ops or something?

They're not supposed to be, but if you only tracked seeks and not
reads or writes, it's hard to be sure what's going on.

8.2's VACUUM should process a btree index (this is a btree index no?)
in physical order, so I'd expect lseeks only when a page is already in
buffers --- at least on the read side. On the write side things might
be a great deal less predictable. You're cleaning out about one tuple
in 30, so the odds are that nearly every index page is getting dirtied,
and they're going to need to be written sometime.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message okparanoid 2007-12-15 00:11:22 update 600000 rows
Previous Message Tom Lane 2007-12-14 23:59:51 Re: VACUUM FREEZE output more than double input