Re: [PERFORM] explanation for seeks in VACUUM

2007-12-14 Thread Jeff Davis
On Fri, 2007-12-14 at 19:04 -0500, Tom Lane wrote: > Jeff Davis <[EMAIL PROTECTED]> 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. The

Re: [PERFORM] explanation for seeks in VACUUM

2007-12-14 Thread Tom Lane
Jeff Davis <[EMAIL PROTECTED]> 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

[PERFORM] explanation for seeks in VACUUM

2007-12-14 Thread Jeff Davis
"bigtable" has about 60M records, about 2M of which are dead at the time of VACUUM. Shared_buffers are about 1GB, and the machine has 4GB of memory. If I run a "SELECT COUNT(*) FROM bigtable", and I ktrace that (FreeBSD) for 10 seconds, I see only a handful of lseek calls (33), which is no surpris

Re: [PERFORM] explanation for seeks in VACUUM (8.2.4)

2007-12-14 Thread Jeff Davis
On Fri, 2007-12-14 at 11:29 -0800, Jeff Davis wrote: > "bigtable" has about 60M records, about 2M of which are dead at the time > of VACUUM. Shared_buffers are about 1GB, and the machine has 4GB of > memory. Forgot to mention: version 8.2.4 Regards, Jeff Davis --