Re: Small fix for inv_getsize - Mailing list pgsql-patches

From Tom Lane
Subject Re: Small fix for inv_getsize
Date
Msg-id 25884.973186358@sss.pgh.pa.us
Whole thread Raw
In response to Re: Small fix for inv_getsize  (Denis Perchine <dyp@perchine.com>)
Responses Re: Small fix for inv_getsize
List pgsql-patches
Denis Perchine <dyp@perchine.com> writes:
>> 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.

            regards, tom lane

pgsql-patches by date:

Previous
From: Denis Perchine
Date:
Subject: Re: Small fix for inv_getsize
Next
From: Denis Perchine
Date:
Subject: Re: Small fix for inv_getsize