From: Tobias Brox <tobias@nordicbet.com>
To: pgsql-performance@postgresql.org
Subject: Planner statistics, correlations
Date: Fri, 12 Jan 2007 09:16:31 +0100
Message-ID: <20070112081631.GA10636@oppetid.no> (raw)
We have a table with a timestamp attribute (event_time) and a state flag
which usually changes value around the event_time (it goes to 4). Now
we have more than two years of events in the database, and around 5k of
future events.
It is important to frequently pick out "overdue events", say:
select * from events where state<>4 and event_time<now()
This query would usually yield between 0 and 100 rows - however, the
planner doesn't see the correlation betewen state and event_time - since
most of the events have event_time<now, the planner also assumes most of
the events with state<>4 has event_time<now, so the expected number of
rows is closer to 5k. This matters, because I have a query with joins,
and I would really benefit from nested loops.
(I've tried replacing "now()" above with different timestamps from the
future and the past. I'm using pg 8.2)
Any suggestions?
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: tobias@nordicbet.com
Subject: Re: Planner statistics, correlations
In-Reply-To: <20070112081631.GA10636@oppetid.no>
* 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