pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Shiar <shiar@shiar.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: bigint index not used
Date: Fri, 26 Mar 2004 18:15:01 -0500
Message-ID: <28354.1080342901@sss.pgh.pa.us> (raw)
In-Reply-To: <20040324121125.GE1178@shiar.org>
References: <20040324121125.GE1178@shiar.org>

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



view thread (2+ messages)

Message-ID: <28354.1080342901@sss.pgh.pa.us>
Permalink:  ../28354.1080342901@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28354.1080342901@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, shiar@shiar.org
  Subject: Re: bigint index not used
  In-Reply-To: <28354.1080342901@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox