AW: RFC: planner statistics in 7.2

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: RFC: planner statistics in 7.2
Date: 2001-04-20 09:58:23
Message-ID: 11C1E6749A55D411A9670001FA68796336829C@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> But you don't really need to look at the index (if it even exists
> at the time you do the ANALYZE). The extent to which the data is
> ordered in the table is a property of the table, not the index.

Think compound, ascending, descending and functional index.
The (let's call it) cluster statistic for estimating indexscan cost can only
be deduced from the index itself (for all but the simplest one column btree).

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-04-20 14:17:24 Re: AW: RFC: planner statistics in 7.2
Previous Message Tom Lane 2001-04-20 02:27:54 Re: RFC: planner statistics in 7.2