Re: pgstattuple extension for indexes
От | Jim C. Nasby |
---|---|
Тема | Re: pgstattuple extension for indexes |
Дата | |
Msg-id | 20060823071419.GI88878@pervasive.com обсуждение исходный текст |
Ответ на | Re: pgstattuple extension for indexes (Satoshi Nagayasu <nagayasus@nttdata.co.jp>) |
Список | pgsql-hackers |
On Fri, Aug 18, 2006 at 09:15:59AM +0900, Satoshi Nagayasu wrote: > ITAGAKI Takahiro wrote: > > But the method has the above problem. So I suggest to use whether > > the right link points to the next adjacent page or not. > > > > if (opaque->btpo_next != P_NONE && opaque->btpo_next != blkno + 1) > > stat->fragments++; > > Well, in that way, following two conditions, > [1] [x] [2] [y] [3] > and > [3] [x] [2] [y] [1] > will be calculated as same fragmentation ratio(100%), I can't agree > with that, because both will generate different costs while index scan > in the real world (I don't care about page splitting algorithm now). What about just reporting the correlation of pages in the index, as well as fragmentation? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-hackers по дате отправления: