From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: 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 14:59:11 -0500
Message-ID: <22246.1103313551@sss.pgh.pa.us> (raw)
In-Reply-To: <200412171152.16130.josh@agliodbs.com>
References: <3D4B6E62-5055-11D9-96E2-000A95DE2550@ifrance.com>
<200412171047.49250.josh@agliodbs.com>
<22121.1103312817@sss.pgh.pa.us>
<200412171152.16130.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.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
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, josh@agliodbs.com, jg@rilk.com
Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)
In-Reply-To: <22246.1103313551@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