Re: Limitations of PostgreSQL

From: "Dean Gibson (DB Administrator)" <postgresql4(at)ultimeth(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Limitations of PostgreSQL
Date: 2005-10-13 16:30:50
Message-ID: 434E8BBA.8040305@ultimeth.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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).
>>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-10-13 16:34:31 Re: Limitations of PostgreSQL
Previous Message Andrew Sullivan 2005-10-13 16:20:53 On "multi-master" (was: Limitations of PostgreSQL)