From: | admin <admin(at)wtbwts(dot)com> |
---|---|
To: | Jeff Eckermann <jeckermann(at)verio(dot)net> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | RE: [GENERAL] Memory leak in FreeBSD? |
Date: | 2000-01-11 13:38:09 |
Message-ID: | Pine.BSF.4.10.10001111335570.59143-100000@server.b0x.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What is maxusers set to in your kernel? One prolem I had was that
postgresql was using more filedescriptors that my kernel could handle. If
you'd like to check your current filedescriptor status and your max, try:
pstat -T. If that is your problem, change your maxusers to a suitable
number and recompile your kernel.
> FreeBSD port: I don't know enough to know what difference that might make.
> Any suggestion you have would be appreciated: thanks.
>
> > Did you upgrade from source or from the freebsd ports?
> >
> > > We upgraded to version 6.5.2 recently, running on FreeBSD 3.0. Now we
> > are
> > > having problems with moderately complex queries failing to complete
> > (backend
> > > terminating unexpectedly; last one crashed the server). The most likely
> > > explanation appears to be a memory leak. Is there any known problem
> > with
> > > FreeBSD?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Inkielman | 2000-01-11 14:23:16 | logs |
Previous Message | Peter Eisentraut | 2000-01-11 13:26:20 | Re: [GENERAL] Dirty workaround to get the results and the errors in the same output file |