Re: Limitations of PostgreSQL - Mailing list pgsql-general

From Dean Gibson (DB Administrator)
Subject Re: Limitations of PostgreSQL
Date
Msg-id 434E8BBA.8040305@ultimeth.com
Whole thread Raw
In response to Re: Limitations of PostgreSQL  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: Limitations of PostgreSQL  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-general
What's the point of a binary search if the list is small enough to fit
on a line or two?  And if a query can be substituted for N1-NN, you have
to read all the values anyway, and then the function is trivially
expressed as a normal query with no decrease in speed.

-- Dean
> On Wed, 2005-10-12 at 20:08, Michael Fuhr wrote:
>
>> Here's an excerpt from the MySQL documentation:
>> INTERVAL(N,N1,N2,N3,...)
>>     Returns 0 if N < N1, 1 if N < N2 and so on or -1 if N is
>>     NULL.  All arguments are treated as integers.  It is required
>>     that N1 < N2 < N3 < ... < Nn for this function to work
>>     correctly.  This is because a binary search is used (very fast).
>>


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Limitations of PostgreSQL
Next
From: Scott Marlowe
Date:
Subject: Re: Limitations of PostgreSQL