Analyze and vacuum, they are sort of mandatory....

From: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Analyze and vacuum, they are sort of mandatory....
Date: 2006-02-11 18:33:39
Message-ID: 16507.24.91.171.78.1139682819.squirrel@mail.mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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, 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 dangerous edge
conditions?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2006-02-11 19:04:27 Re: Locks
Previous Message Alfranio Correia Junior 2006-02-11 18:30:14 Lock Functions