| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.3.4 vacuum/analyze error |
| Date: | 2004-09-30 14:01:04 |
| Message-ID: | 20040930140104.GB5151@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-09-30 14:03:29 | Re: dangling permission on tables after drop user. |
| Previous Message | Vivek Khera | 2004-09-30 13:32:30 | Re: dangling permission on tables after drop user. |