Re: analyze.c

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tiago Antão <tra(at)fct(dot)unl(dot)pt>
Cc: PostgreSQL Hackers list <pgsql-hackers(at)hub(dot)org>
Subject: Re: analyze.c
Date: 2000-10-15 18:20:56
Message-ID: 200010151820.OAA09211@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hi!
>
> About analyze.c:
> If taken out vacuum, couldn't it be completly taken out of pg? Say,
> to an external program? What's the big reason not to do that? I know that
> there is some code in analyze.c (like comparing) that uses other parts of
> pg, but that seems to be easily fixed.
>
> I'm leaning toward the implementation of end-biased histograms. There is
> an introductory reference in the IEEE Data Engineering Bulletin, september
> 1995 (available on microsoft research site).

Why take it out of the backend? Seems like a real pain, especially when
you realize what functions it would have to call.

Also, keep in mind that the current analyze generates perfect estimates for
columns containing only two unique values, and columns containing only
unique values. All other cases generate imperfect statistics.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

  • analyze.c at 2000-08-23 11:18:19 from Tiago Antão

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-10-15 18:22:30 Re: analyze.ct
Previous Message Stephan Szabo 2000-10-15 17:16:32 Re: select oid .... for update ....