Re: Bitmap scans vs. the statistics views

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Jan Wieck <JanWieck(at)yahoo(dot)com>
Subject: Re: Bitmap scans vs. the statistics views
Date: 2005-04-22 19:42:02
Message-ID: 200504221242.02774.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> I've never fully understood the distinction the stats make between
> "tuples fetched" and "tuples returned", and it's even less obvious how
> to apply it when the index and heap operations are decoupled.

Well, it's mainly a counter to measure how many dead rows are in your active
data set. It probably belongs elsewhere, such as pg_stats_all_tables with
the overall fetch counts.

> In
> particular the function design assumes that heap tuple fetches can be
> tied to particular indexes, which is now a broken assumption. You
> might be amused by this test case I just finished debugging:

Well, I'd be in favor of moving the "useful" version of tuples_returned to
pg_stat_*_tables as an overall count. However, we cant drop the column from
pg_stat_indexes without breaking apps; at best, we'd have to warn people of
the accuracy issues and give it a few versions before we dropped it.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2005-04-22 19:47:35 Re: Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords
Previous Message Jan Wieck 2005-04-22 19:36:00 Re: Bitmap scans vs. the statistics views