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

From Denis Perchine
Subject Re: Small fix for inv_getsize
Date
Msg-id 0011022357100I.31936@dyp.perchine.com
Whole thread Raw
In response to Re: Small fix for inv_getsize  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Small fix for inv_getsize  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
> >> Hmm ... probably right, but the loop logic doesn't behave that way
> >> right now.
> >
> > Why not... Did not I explained what happend there?
>
> You didn't read the way I changed it: right now it scans all the tuples
> and takes the maximum endpoint, rather than assuming they will be read
> in any particular order.

OK. I see... I just wondering whether it is possible to use index to get the
maximum...

--
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Small fix for inv_getsize
Next
From: Tom Lane
Date:
Subject: Re: Small fix for inv_getsize