On 9/27/05 7:45 AM, "Yonatan Ben-Nes" <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
>> "Cristian Prieto" <[EMAIL PROTECTED]> writes:
>>
>>> mydb=# explain analyze select locid from geoip_block where
>>> '216.230.158.50'::inet between start_block and end_block;
>>
>>
>>> As you see it still using
Tom Lane wrote:
"Cristian Prieto" <[EMAIL PROTECTED]> writes:
mydb=# explain analyze select locid from geoip_block where
'216.230.158.50'::inet between start_block and end_block;
As you see it still using a sequential scan in the table and ignores the
index, any other suggestion?
That tw
Cristian Prieto wrote:
mydb=# explain analyze select locid from geoip_block where
'216.230.158.50'::inet between start_block and end_block;
QUERY PLAN
-
"Cristian Prieto" <[EMAIL PROTECTED]> writes:
> mydb=# explain analyze select locid from geoip_block where
> '216.230.158.50'::inet between start_block and end_block;
> As you see it still using a sequential scan in the table and ignores the
> index, any other suggestion?
That two-column index is
g a sequential scan in the table and ignores the
index, any other suggestion?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean Davis
Sent: Lunes, 26 de Septiembre de 2005 10:24 a.m.
To: Cristian Prieto; pgsql-general@postgresql.org
Subject: Re: [GENERAL]
On 9/26/05 11:26 AM, "Cristian Prieto" <[EMAIL PROTECTED]> wrote:
>
> Hello pals, I have the following table in Postgresql 8.0.1
>
> Mydb# \d geoip_block
> Table "public.geoip_block"
> Column| Type | Modifiers
> -++---
> locid | bigint |
> start_block | i
Hello pals, I have the following table in Postgresql 8.0.1
Mydb# \d geoip_block
Table "public.geoip_block"
Column| Type | Modifiers
-++---
locid | bigint |
start_block | inet |
end_block | inet |
mydb# explain analyze select locid from geoip_bl
