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

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, 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 21:23:45
Message-ID: 20041217212345.GC2119@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Dec 17, 2004 at 14:46:57 -0500,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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.

Shouldn't that be 7.4.6? I am expecting there to be an eventual 7.4.7
because of some post 7.4.6 fixes that have gone in, but I haven't seen
any other indications that this has already happened.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Steinar H. Gunderson 2004-12-17 21:56:27 Re: Seqscan rather than Index
Previous Message Tom Lane 2004-12-17 21:17:29 Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory)