Re: 7.3.4 vacuum/analyze error - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: 7.3.4 vacuum/analyze error
Date
Msg-id 20040930140104.GB5151@dcc.uchile.cl
Whole thread Raw
In response to Re: 7.3.4 vacuum/analyze error  ("Ed L." <pgsql@bluepolka.net>)
Responses Re: 7.3.4 vacuum/analyze error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wed, Sep 29, 2004 at 11:23:52PM -0600, Ed L. wrote:
> On Wednesday September 29 2004 5:17, Tom Lane wrote:
> > >
> > > 2004-09-29 18:14:53.621 [520]    ERROR:  Memory exhausted in
> > > AllocSetAlloc(1189)
> > >
> > > Analyze: 132263832 total in 27 blocks; 2984 free (35 chunks); 132260848
> > > used
> >
> > Either increase your per-process memory limit, or reduce the statistics
> > targets for this table ...
>
> Can you explain a little more of how you interpret the numbers above to draw
> your conclusion?

I just means that, from the operating system POV, there are 132263832
bytes in use.  The rest is Pg internal bookkeeping that doesn't help you
any.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Uno combate cuando es necesario... ¡no cuando está de humor!
El humor es para el ganado, o para hacer el amor, o para tocar el
baliset.  No para combatir."  (Gurney Halleck)


pgsql-general by date:

Previous
From: Vivek Khera
Date:
Subject: Re: dangling permission on tables after drop user.
Next
From: Alvaro Herrera
Date:
Subject: Re: dangling permission on tables after drop user.