pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: John Siracusa <siracusa@mindspring.com>
To: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Re: Column correlation drifts, index ignored again
Date: Sun, 22 Feb 2004 11:05:57 -0800
Message-ID: <200402221105.57068.josh@agliodbs.com> (raw)
In-Reply-To: <94FA2D7A-64CC-11D8-9DEA-000A95BA4506@mindspring.com>
References: <94FA2D7A-64CC-11D8-9DEA-000A95BA4506@mindspring.com>

On Saturday 21 February 2004 16:18, John Siracusa wrote:
John,

> Next, thanks to my earlier thread, I clustered the table on the date
> column and then "SET STATISTICS" on the date column to be 100.  That
> did the trick, and I stopped explicitly disabling seqscan.

100?  Are you sure you don't mean some other number?   100 is not very high 
for problem analyze issues.  You might try 500.   Generally when I have a 
problem query I raise stats to something like 1000 and drop it down until the 
problem behaviour starts re-appearing.

>      date_trunc('day', date) AS date

Have you tried putting an index on date_trunc('day', date) and querying on 
that instead of using this:

>      date BETWEEN '2004-02-01 00:00:00' AND '2004-02-28 23:59:59'

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (16+ messages)  latest in thread

Message-ID: <200402221105.57068.josh@agliodbs.com>
Permalink:  ../200402221105.57068.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200402221105.57068.josh@agliodbs.com

 · 

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: josh@agliodbs.com, siracusa@mindspring.com
  Subject: Re: Column correlation drifts, index ignored again
  In-Reply-To: <200402221105.57068.josh@agliodbs.com>

* 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