From: | Jim Nasby <jim(at)nasby(dot)net> |
---|---|
To: | tv(at)fuzzy(dot)cz |
Cc: | "Csaba Nagy" <ncslists(at)googlemail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: estimating # of distinct values |
Date: | 2011-01-07 19:56:12 |
Message-ID: | E42C65A0-A7C3-4FE1-877F-555E1C7836F4@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 7, 2011, at 5:32 AM, tv(at)fuzzy(dot)cz wrote:
> Another thing I'm not sure about is where to store those intermediate
> stats (used to get the current estimate, updated incrementally). I was
> thinking about pg_stats but I'm not sure it's the right place - depending
> on the algorithm, this may be a fet kilobytes up to several megabytes. And
> it's not needed except when updating it. Any ideas?
If you're using it essentially as a queue, maybe a resource fork makes sense?
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Jacobson | 2011-01-07 19:57:34 | Re: obj_unique_identifier(oid) |
Previous Message | Tom Lane | 2011-01-07 19:51:39 | Re: system views for walsender activity |