Re: seq scan over 3.3 million rows instead of single keyindex access

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: pgsql-performance@xxxxxxxxxxxxxx
Subject: Re: seq scan over 3.3 million rows instead of single keyindex access
From: "Andrus" <kobruleht2@xxxxxx>
Date: Sun, 23 Nov 2008 13:43:08 +0200
In-reply-to: <20081123081024.GA7443@tux>
Organization: Hub.Org Networking Services
References: <gg9pg7$1edv$2@xxxxxxxxxxxx> <20081123081024.GA7443@tux>

An index-scan makes only sense if rid contains considerable more than3000000 rows.


I'm sorry, I meant using index to get the row.

Andrus.


--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

References:
- seq scan over 3.3 million rows instead of single key index access
  - From: Andrus
- Re: seq scan over 3.3 million rows instead of single key index access
  - From: Andreas Kretschmer

Prev by Date: Re: seq scan over 3.3 million rows instead of single key index access
Next by Date: Re: Hash join on int takes 8..114 seconds
Previous by thread: Re: seq scan over 3.3 million rows instead of single key index access
Next by thread: Re: seq scan over 3.3 million rows instead of single key index access
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux