Skip site navigation (1) Skip section navigation (2)

Re: Use of sequence rather than index scan for one text column on one instance of a database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bill Kirtley <bill(at)actbluetech(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Use of sequence rather than index scan for one text column on one instance of a database
Date: 2009-09-24 15:34:53
Message-ID: 24043.1253806493@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Bill Kirtley <bill(at)actbluetech(dot)com> writes:
> For what it's worth:

> select xmin,* from pg_index where indexrelid =  
> 'users_key_index'::regclass;
>   xmin | indexrelid | indrelid | indnatts | indisunique | indisprimary  
> | indisclustered | indisvalid | indcheckxmin | indisready | indkey |  
> indclass | indoption | indexprs | indpred
> ------+------------+----------+----------+-------------+-------------- 
> +----------------+------------+--------------+------------+-------- 
> +----------+-----------+----------+---------
>   1006 |   15076176 |    17516 |        1 | f           | f             
> | f              | t          | f            | t          | 10      
> |    10042 | 0         |          |

Uh ... 'users_key_index'?  What's that?  What would actually be the most
useful is to compare the pg_index entries for the working and
non-working indexes (the ones on email and key).

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Karl DenningerDate: 2009-09-24 15:48:34
Subject: Re: High CPU load on Postgres Server during Peak times!!!!
Previous:From: Andy ColsonDate: 2009-09-24 15:32:21
Subject: Re: High CPU load on Postgres Server during Peak times!!!!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group