| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [QUESTIONS] Maybe a Vacuum bug in 6.3.2 |
| Date: | 1998-05-13 01:29:00 |
| Message-ID: | Pine.BSF.3.96.980512222706.438l-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Figuring that, for now, this might be more an admin related question then
anything, redirected appropriately...
-hackers is not for bug reports, it is for development related issues...
On Sat, 9 May 1998, Michael Richards wrote:
> under top the backend just keeps growing.
> 492 postgres 85 0 16980K 19076K RUN 1:43 91.67% 91.48% postgres
> when it hit about 20 megs, it craps out. Swap space is 0% used, and I am
> not even convinced this is using all 128 megs of ram either. Could
> something like memory fragementation be an issue?
>
> Does anyone have any ideas other than buying a gig of ram?
Just a thought (long shot, at that)...what are your limits set at
when you start up the postmaster? Are you hitting a limit, with the
postmaster reporting it as an inability to allocate more memory?
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 1998-05-13 03:04:55 | No Space left error... |
| Previous Message | Peter Mount | 1998-05-12 22:43:15 | Re: [ADMIN] Setup and LIBPQ (Newbie) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-05-13 04:55:42 | Re: [HACKERS] Unusual notices in latest snapshot |
| Previous Message | The Hermit Hacker | 1998-05-13 01:07:41 | Re: [HACKERS] OK to send e-mail? |