Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-12 Thread Jim Buttafuoco
lt;[EMAIL PROTECTED]> Cc: "Mark Woodward" <[EMAIL PROTECTED]>, pgsql-hackers@postgresql.org Sent: Sun, 12 Feb 2006 11:18:03 -0500 Subject: Re: [HACKERS] Analyze and vacuum, they are sort of mandatory > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > Yes, that is w

Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-12 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Yes, that is what autovacuum does. It detects changes in the database > and runs analyze if failing to do so would cause PostgreSQL to behave > badly. I don't know why it's not turned on by default. Conservatism. It may well be on by default in s

Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-12 Thread Mark Woodward
> Mark Woodward wrote: >> My question was based on an observation that ANALYZE and VACUUM are >> nessisary, both for different reasons. The system or tools must be >> able to detect substantial changes in the database and at least run >> analyze if failing to do so would cause PostgreSQL to fail ba

Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-12 Thread Peter Eisentraut
Mark Woodward wrote: > My question was based on an observation that ANALYZE and VACUUM are > nessisary, both for different reasons. The system or tools must be > able to detect substantial changes in the database and at least run > analyze if failing to do so would cause PostgreSQL to fail badly.

Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-12 Thread Mark Woodward
> Mark Woodward wrote: >> I know this is a kind of stupid question, but postgresql does not >> behave well when the system changes in a major way without at least >> an analyze. There must be something that can be done to protect the >> casual user (or busy sometimes absent minded developer) from t

Re: [HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-11 Thread Peter Eisentraut
Mark Woodward wrote: > I know this is a kind of stupid question, but postgresql does not > behave well when the system changes in a major way without at least > an analyze. There must be something that can be done to protect the > casual user (or busy sometimes absent minded developer) from these >

[HACKERS] Analyze and vacuum, they are sort of mandatory....

2006-02-11 Thread Mark Woodward
I was think about how forgetting to run analyze while developing a table loader program caused PostgreSQL to run away and use up all the memory. Is there some way that postges or psql can know that it substantially altered the database and run analyze? I know this is a kind of stupid question, bu