From: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: HOT pgbench results |
Date: | 2007-08-07 15:26:15 |
Message-ID: | E1539E0ED7043848906A8FF995BDA5790242290C@m0143.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > unpatched HOT
> > autovacuums 116 43
> > autoanalyzes 139 60
>
> > HOT greatly reduces the number of vacuums needed. That's
> good, that's
> > where the gains in throughput in longer I/O bound runs comes from.
>
> But surely failing to auto-analyze after a HOT update is a bad thing.
Well, the definition is that no index columns changed, so this seems
debateable.
It seems for OLTP you should not need an analyze, but for DSS filtering
or joining
on non indexed columns you would. And that would also only be relevant
if you created
custom statistics on non indexed columns.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-08-07 15:39:52 | Re: More logging for autovacuum |
Previous Message | Gregory Stark | 2007-08-07 15:23:50 | Re: More logging for autovacuum |