Re: Small fix for inv_getsize
От | Denis Perchine |
---|---|
Тема | Re: Small fix for inv_getsize |
Дата | |
Msg-id | 0011022335200G.31936@dyp.perchine.com обсуждение исходный текст |
Ответ на | Re: Small fix for inv_getsize (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Small fix for inv_getsize
|
Список | pgsql-patches |
> >> Now that I think about it, this code could do a two-key scan backwards > >> and stop after finding the first (last) valid tuple, but that's more > >> than a one-line change. > > > > Actual logic is to find the maximum of pageno, for specified oid. > > I do index scan on 2-keys index, specifying only one key as constraint... > > If I do index scan forward I will get the smallest pageno first... > > Otherwise I get the highest pageno... And this is what I want... > > Hmm ... probably right, but the loop logic doesn't behave that way > right now. Why not... Did not I explained what happend there? obj_desc->index_r is 2 key index... I do index scan backward. Get first valid tuple... What I miss... Can you please give me the correct one... I am totally confused... Sorry for asking this... -- Sincerely Yours, Denis Perchine ---------------------------------- E-Mail: dyp@perchine.com HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ----------------------------------
В списке pgsql-patches по дате отправления: