From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Mount <peter@retep.org.uk>
Cc: Pablo Saul Salazar - CESERCOMP <ssalazar@goliat.espol.edu.ec>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] table very big !!!!!
Date: Mon, 22 Nov 1999 19:06:49 -0500
Message-ID: <25736.943315609@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.10.9911222036200.19044-100000@maidast.retep.org.uk>
Peter Mount <peter@retep.org.uk> writes:
> Ah, try running first vacuum; then vacuum analyze. The first one will
> truncate the table removing the wasted space. The second simply rebuilds
> some statistics about the table.
This is not right --- AFAICT, vacuum *always* runs the compaction phase.
You can allow or skip the stats-gathering phase by specifying "analyze"
or not, but "vacuum analyze" implies "vacuum".
It sounds like Pablo has a problem with vacuum not doing what it is
supposed to ... has anyone else ever seen that? It's a new one on me.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter@retep.org.uk, ssalazar@goliat.espol.edu.ec
Subject: Re: [INTERFACES] table very big !!!!!
In-Reply-To: <25736.943315609@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox