From: | Jeff Eckermann <jeckermann(at)verio(dot)net> |
---|---|
To: | "'admin'" <admin(at)wtbwts(dot)com> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | RE: [GENERAL] Memory leak in FreeBSD? |
Date: | 2000-01-11 19:01:58 |
Message-ID: | 79103FDEF940D2118D9D00A0C9C9309CA35F9B@NEZU |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Maxusers is set to 128. RAM is 256Mg.
Do you think this could be the problem?
> -----Original Message-----
> From: admin [SMTP:admin(at)wtbwts(dot)com]
> Sent: Tuesday, January 11, 2000 12:50 PM
> To: Jeff Eckermann
> Cc: 'pgsql-general(at)postgresql(dot)org'
> Subject: RE: [GENERAL] Memory leak in FreeBSD?
>
> 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 | Ed Loehr | 2000-01-11 19:13:28 | Re: [GENERAL] Question on timestamp in psql |
Previous Message | Jeff Eckermann | 2000-01-11 18:28:21 | RE: [GENERAL] Memory leak in FreeBSD? |