* Jeff Eckermann <jeckermann@verio.net> [000111 11:37] wrote:
>
> > -----Original Message-----
> > From: admin [SMTP:admin@wtbwts.com]
> > Sent: Tuesday, January 11, 2000 12:50 PM
> > To: Jeff Eckermann
> > Cc: 'pgsql-general@postgresql.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.
> >
>
> Maxusers is set to 128. RAM is 256Mg.
> Do you think this could be the problem?
Saying it's a memory leak without describing any other sort of symptoms is
not a very useful bug report. Twiddling maxusers should have _no_ effect
on whether an application leaks memory or not.
So how about you explain the symptoms of the 'leak' (kernel messages,
top, systat -vmstat) and what exactly you mean by it. Does the postmaster
gradually increase in memory size until the machine starts swapping? If
not, then it's probably _not_ a memory leak.
thanks,
-Alfred Perlstein - [bright@rush.net|alfred@freebsd.org]
Wintelcom systems administrator and programmer
- http://www.wintelcom.net/ [bright@wintelcom.net]
> > > 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?
> > >
> >
> >
> > ************
>
> ************
