Re: bigint index not used - Mailing list pgsql-performance

From Tom Lane
Subject Re: bigint index not used
Date
Msg-id 28354.1080342901@sss.pgh.pa.us
Whole thread Raw
In response to bigint index not used  (Shiar <shiar@shiar.org>)
List pgsql-performance
Shiar <shiar@shiar.org> writes:
>> EXPLAIN ANALYZE SELECT id FROM userinfo WHERE icq <> '0';
>  Seq Scan on userinfo  (cost=0.00..47355.90 rows=849244 width=4) (actual time=0.563..1222.963 rows=48797 loops=1)
>    Filter: (icq <> 0::bigint)
>  Total runtime: 1258.703 ms

The rows estimate is way off, which might or might not have much to do
with the issue, but it's surely suspicious.

> We're running PostgreSQL 7.4.1 on a Debian/Linux 2.4 system with 4GB RAM and a
> fast SCSI RAID array, with settings:

Update to 7.4.2 and follow the procedure in the release notes about
fixing pg_statistic; that may make things better.  int8 columns are
vulnerable to the statistic misalignment bug.

            regards, tom lane

pgsql-performance by date:

Previous
From: CoL
Date:
Subject: Re: Databases Vs. Schemas
Next
From: Steve Atkins
Date:
Subject: Re: [HACKERS] fsync method checking