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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-patches by date

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