| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | pgsql(at)mohawksoft(dot)com, sugita(at)srapc1327(dot)sra(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Incorrect expected rows by ANALYZE |
| Date: | 2003-04-07 15:39:59 |
| Message-ID: | 252.1049729999@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 7 Apr 2003 pgsql(at)mohawksoft(dot)com wrote:
>> Couldn't there be an ANALYZE FULL option?
It already gets the row count right if you did VACUUM ANALYZE. I don't
think we need ANALYZE FULL (at least, not for this purpose).
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> There's something close, that is, you can change the statistics target for
> a column in a table like so:
> ALTER TABLE [ ONLY ] table [ * ]
> ALTER [ COLUMN ] column SET STATISTICS integer
> which can make it so that more of the rows are analyzed.
I'm not sure though how effective that will be at avoiding the problem
Kenji is complaining of.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2003-04-07 15:45:07 | Re: more contrib: log rotator |
| Previous Message | scott.marlowe | 2003-04-07 15:35:07 | Re: more contrib: log rotator |