Skip site navigation (1) Skip section navigation (2)

Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: Pailloncy Jean-Gerard <jg(at)rilk(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)
Date: 2004-12-17 19:59:11
Message-ID: 22246.1103313551@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Jean-Gerard, can you put together a self-contained test case? I suspect
>> it need only look like "put some data in a table, make a tsearch2 index,
>> delete half the rows in the table, VACUUM FULL". But I don't have time
>> to try to cons up a test case right now, and especially not to figure
>> out what to do to duplicate your problem if it doesn't happen on the
>> first try.

> Might be hard.  I have 2 databases with Tsearch2 on 7.4, and haven't seen any
> such problem.  Including one that blows away about 3000 rows a day.

Yeah, I'm sure there is some particular thing Jean-Gerard is doing that
is triggering the problem.  He can probably boil his existing table down
to a test case faster than we can guess what the trigger condition is.

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Stan YDate: 2004-12-17 21:10:46
Subject: Monitor CPU time per transaction?
Previous:From: Josh BerkusDate: 2004-12-17 19:52:15
Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group