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:53:23
Message-ID: 26028.973187603@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Denis Perchine <dyp(at)perchine(dot)com> writes:
>> 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.

			regards, tom lane

In response to

Responses

pgsql-patches by date

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

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