| From: | "Gordon A(dot) Runkle" <gar(at)integrated-dynamics(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Odd statistics behaviour in 7.2 |
| Date: | 2002-02-13 21:10:04 |
| Message-ID: | 1013634607.21157.148.camel@spiff.runkleinc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2002-02-13 at 13:02, Tom Lane wrote:
[ Lots of enlightening info ]
Thanks, Tom!
Would it be fair to say that the correct workaround for now would
be to use ALTER TABLE SET STATISTICS on columns of interest which have
this near-unique characteristic?
Does ALTER TABLE SET STATISTICS only increase the histogram size, or
does it also cause more rows to be sampled? If not, how would one
increase the sample size (assuming this would be desirable)?
I have quite a few tables that have columns of interest with near-unique
values, so I'm keenly interested. I'm sorry I didn't have time to do all
this testing during the beta phase, there just wasn't time. :-(
Thanks again,
Gordon.
--
"Far and away the best prize that life has to offer
is the chance to work hard at work worth doing."
-- Theodore Roosevelt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-13 21:34:27 | Re: Odd statistics behaviour in 7.2 |
| Previous Message | Peter Eisentraut | 2002-02-13 20:28:24 | When and where to check for function permissions |