Skip site navigation (1) Skip section navigation (2)

Re: Small fix for inv_getsize

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Denis Perchine <dyp(at)perchine(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Small fix for inv_getsize
Date: 2000-11-02 17:32:38
Message-ID: 25884.973186358@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Denis Perchine <dyp(at)perchine(dot)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

In response to

Responses

pgsql-patches by date

Next:From: Denis PerchineDate: 2000-11-02 17:35:20
Subject: Re: Small fix for inv_getsize
Previous:From: Denis PerchineDate: 2000-11-02 17:02:23
Subject: Re: Small fix for inv_getsize

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group