From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pailloncy Jean-Gerard <jg@rilk.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)
Date: Fri, 17 Dec 2004 17:20:47 -0500
Message-ID: <24692.1103322047@sss.pgh.pa.us> (raw)
In-Reply-To: <DFED184A-5076-11D9-96E2-000A95DE2550@rilk.com>
References: <3D4B6E62-5055-11D9-96E2-000A95DE2550@ifrance.com>
<DFED184A-5076-11D9-96E2-000A95DE2550@rilk.com>
Pailloncy Jean-Gerard <jg@rilk.com> writes:
> Update to my case:
> I drop and recreate the index and there was no problem this time.
> Strange...
Well, that time there wasn't actually any work for VACUUM FULL to do.
I think the bloat is probably driven by having to move a lot of rows
in order to shrink the table. That means creating and deleting a lot
of index entries.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jg@rilk.com
Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)
In-Reply-To: <24692.1103322047@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