pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 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 16:58:30 -0500
Message-ID: <BC5E9036.2DCA2%siracusa@mindspring.com> (raw)
In-Reply-To: <200402221105.57068.josh@agliodbs.com>

On 2/22/04 2:05 PM, Josh Berkus wrote:
> On Saturday 21 February 2004 16:18, John Siracusa wrote:
>> 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.

IIRC, 100 was the number suggested in the earlier thread.  I did set it to
500 yesterday, I believe.  We'll see how that goes.

> 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.

Since this problem takes a long time to appear (months), that cycle could
take a long time... :)

>>      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'

No, but then I'd just have a different index to persuade the planner to use
:)  Not every query does date_trunc() stuff, but they all do date ranges,
often at a granularity of seconds.

-John




view thread (16+ messages)  latest in thread

Message-ID: <BC5E9036.2DCA2%siracusa@mindspring.com>
Permalink:  ../BC5E9036.2DCA2%25siracusa@mindspring.com/
Also on:    postgresql.org/message-id/BC5E9036.2DCA2%siracusa@mindspring.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: siracusa@mindspring.com
  Subject: Re: Column correlation drifts, index ignored again
  In-Reply-To: <BC5E9036.2DCA2%siracusa@mindspring.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