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

Re: Small fix for inv_getsize

From: Denis Perchine <dyp(at)perchine(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Small fix for inv_getsize
Date: 2000-11-02 17:35:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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(at)perchine(dot)com
FidoNet: 2:5000/120.5

In response to


pgsql-patches by date

Next:From: Tom LaneDate: 2000-11-02 17:53:23
Subject: Re: Small fix for inv_getsize
Previous:From: Tom LaneDate: 2000-11-02 17:32:38
Subject: Re: Small fix for inv_getsize

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