pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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:46:57 -0500
Message-ID: <22121.1103312817@sss.pgh.pa.us> (raw)
In-Reply-To: <200412171047.49250.josh@agliodbs.com>
References: <3D4B6E62-5055-11D9-96E2-000A95DE2550@ifrance.com>
	<07F4E72A-5059-11D9-96E2-000A95DE2550@ifrance.com>
	<FED87045-5059-11D9-96E2-000A95DE2550@rilk.com>
	<200412171047.49250.josh@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:
> Jean-Gerard,
>> When backend hits the tsearch2 index, SIZE/RES grows until it reachs
>> 1GB, where I got the error.
>> PID    UID   PRI NICE  SIZE   RES STATE WAIT     TIME    CPU COMMAND
>> 20461    503    -5    0  765M  824M sleep biowai   4:26 33.20% postgres

> OK, next thing to try is upgrading to 7.4.7.   Since you have 7.4.2, this 
> should be a straightforward binary replacement.

This looks like it must be a memory leak in the gist indexing code
(either gist itself or tsearch2).  I don't see any post-release fixes in
the 7.4 branch that look like they fixed any such thing :-(, so it's
probably still there in 7.4.7, and likely 8.0 too.

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.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <22121.1103312817@sss.pgh.pa.us>
Permalink:  ../22121.1103312817@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22121.1103312817@sss.pgh.pa.us

 · 

reply

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: <22121.1103312817@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