Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
От | Rod Taylor |
---|---|
Тема | Re: [PERFORM] Bad n_distinct estimation; hacks suggested? |
Дата | |
Msg-id | 1114560992.77587.112.camel@home обсуждение исходный текст |
Ответ на | Re: [PERFORM] Bad n_distinct estimation; hacks suggested? (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
|
Список | pgsql-hackers |
On Tue, 2005-04-26 at 19:28 -0400, Greg Stark wrote: > Rod Taylor <rbt@sitesell.com> writes: > > > On Tue, 2005-04-26 at 19:03 -0400, Greg Stark wrote: > > > This one looks *really* good. > > > > > > http://www.aladdin.cs.cmu.edu/papers/pdfs/y2001/dist_sampl.pdf > > > > > > It does require a single full table scan > > > > Ack.. Not by default please. > > > > I have a few large append-only tables (vacuum isn't necessary) which do > > need stats rebuilt periodically. > > The algorithm can also naturally be implemented incrementally. Which would be > nice for your append-only tables. But that's not Postgres's current philosophy > with statistics. Perhaps some trigger function that you could install yourself > to update statistics for a newly inserted record would be useful. If when we have partitions, that'll be good enough. If partitions aren't available this would be quite painful to anyone with large tables -- much as the days of old used to be painful for ANALYZE. --
В списке pgsql-hackers по дате отправления: