pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
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 10:47:49 -0800
Message-ID: <200412171047.49250.josh@agliodbs.com> (raw)
In-Reply-To: <FED87045-5059-11D9-96E2-000A95DE2550@rilk.com>
References: <3D4B6E62-5055-11D9-96E2-000A95DE2550@ifrance.com>
	<07F4E72A-5059-11D9-96E2-000A95DE2550@ifrance.com>
	<FED87045-5059-11D9-96E2-000A95DE2550@rilk.com>

Jean-Gerard,

> The classic output from top (during all other index vacuum):
>    PID    UID   PRI NICE  SIZE   RES STATE WAIT     TIME    CPU COMMAND
> 20461    503    14    0   13M   75M sleep semwai   5:27  2.05% postgres
>
> 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.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco



view thread (12+ messages)  latest in thread

Message-ID: <200412171047.49250.josh@agliodbs.com>
Permalink:  ../200412171047.49250.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200412171047.49250.josh@agliodbs.com

 · 

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: josh@agliodbs.com, jg@rilk.com
  Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)
  In-Reply-To: <200412171047.49250.josh@agliodbs.com>

* 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