On Tue, Jul 03, 2001 at 05:12:43PM +0100, Richard Huxton wrote:
: VACUUM ANALYZE frequency depends on numbers of updates. I believe someone
: has been looking at a way of doing this in the background.
Oh yeah, definitely depends on updates, or rather, changes to the
table contents (insertions, de
On Tue, Jul 03, 2001 at 10:42:37AM -0400, Sam Tregar wrote:
: On Tue, 3 Jul 2001, Philip Molter wrote:
:
: > What causes this and how can I fix it?
:
: Have you tried a VACUUM ANALYZE? For some reason Postgres isn't able to
: use its indexes fully unless you VACUUM ANALYZE often.
:
: I conside
On Tue, 3 Jul 2001, Philip Molter wrote:
> What causes this and how can I fix it?
Have you tried a VACUUM ANALYZE? For some reason Postgres isn't able to
use its indexes fully unless you VACUUM ANALYZE often.
I consider this a bug but I gather the developers are OK with it.
-sam
---
Is there any way to force the query optimizer to prefer one scan type
over another? I have a rather large query which the optimizer sometime
last night decided to switch from using index scans in a variety of
places to using sequential scans. This has resulted in a doubling of
CPU usage and weir
