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:57:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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 

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: Denis PerchineDate: 2000-11-02 17:59:04
Subject: Re: Small fix for inv_getsize
Previous:From: Tom LaneDate: 2000-11-02 17:53:23
Subject: Re: Small fix for inv_getsize

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