Re: Thoughts on statistics for continuously advancing columns - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Thoughts on statistics for continuously advancing columns
Date
Msg-id 7216.1262142513@sss.pgh.pa.us
Whole thread Raw
In response to Thoughts on statistics for continuously advancing columns  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Thoughts on statistics for continuously advancing columns  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: Thoughts on statistics for continuously advancing columns  (Peter Eisentraut <peter_e@gmx.net>)
Re: Thoughts on statistics for continuously advancing columns  (Chetan Suttraway <chetan.suttraway@enterprisedb.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> My thoughts on dealing with this intelligently without a major change to
> statstics gathering went along these lines:

> 1. add columns to pg_statistic to hold estimates of upper and lower
> bounds growth between analyzes.

This seems like a fundamentally broken approach, first because "time
between analyzes" is not even approximately a constant, and second
because it assumes that we have a distance metric for all datatypes.
(Note that convert_to_scalar does not assume that it can measure
arbitrary distances, but only fractions *within* a histogram bucket;
and even that is pretty shaky.)

I don't have a better idea at the moment :-(
        regards, tom lane


pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION
Next
From: Bruce Momjian
Date:
Subject: Re: Serializable implementation