| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE and index/stats degradation |
| Date: | 2007-07-02 15:17:20 |
| Message-ID: | 87tzsm4yyn.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> Actually, come to think of it, I don't think I'd want any vacuums at all
> on this particular table. Just the analyze on the primary key, no
> vacuums, no statistics on anything else. Unfortunately it's not just one
> table, but a set of tables that can be created dynamically. I could
> change that, but in this particular case I don't think I should.
The way you described it there were records being inserted and later deleted.
Why wouldn't you need vacuums?
Or are all the records eventually deleted and then the table truncated or
dropped before the next batch of inserts?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-07-02 15:51:10 | Re: Configurable Additional Stats |
| Previous Message | Jeroen T. Vermeulen | 2007-07-02 13:07:13 | Re: ANALYZE and index/stats degradation |