Re: pgsql: When estimating the selectivity of an inequality "column >

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql: When estimating the selectivity of an inequality "column >
Date: 2010-01-04 14:50:21
Message-ID: 20100104145021.GB3778@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Greg Stark wrote:

> I also wonder if we want to run these lookups on every single planner
> invocation. If the table is being rarely updated analyze will never
> fire and the stats value will never be updated. I don't think we want
> the planner doing write operations to the stats either though. It
> would be nice if there was a low-cost mode of operation for ANALYZE
> which simulates precisely this update, the planner could send a stats
> message saying that autovacuum should schedule one of these operations
> sometime even if it doesn't see a need for a full analyze run.

Maybe autovac could run such a cheap ANALYZE frequently on tables with
large number of inserts (but not large enough to trigger a regular
ANALYZE) ... say a fixed number of tuples (not depending on pg_class.reltuples)

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Greg Stark 2010-01-04 15:50:03 Re: pgsql: When estimating the selectivity of an inequality "column >
Previous Message Greg Stark 2010-01-04 13:29:52 Re: pgsql: When estimating the selectivity of an inequality "column >

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-04 14:59:48 Re: quoting psql varible as identifier
Previous Message Andrew Dunstan 2010-01-04 14:44:53 Re: invalid UTF-8 via pl/perl