Re: [HACKERS] Postmaster options, process spawning, logging, etc.

From: Tim Holloway <mtsinc(at)southeast(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Matthew Hagerty <matthew(at)venux(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Postmaster options, process spawning, logging, etc.
Date: 1999-12-16 19:26:58
Message-ID: 38593D02.652337C7@southeast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ah. I hadn't noticed they were that far back. I've passed your news on
to our distraught friends in Columbia with a suggestion to try the 6.5.3
RPM.

Tom Lane wrote:
>
> Tim Holloway <mtsinc(at)southeast(dot)net> writes:
> > 1. Matthew's problem sounds an awful lot like what's being reported
> > by Lucio Andres Perez in v6.4.2. Maybe some kind of bug in detecting
> > and handling over-the-limit backends.
>
> 6.4.* didn't really have any check/defense against spawning more
> backends than it had resources for. 6.5 does check and enforce the
> maxbackends limit. It's certainly possible that Matthew's running into
> some kind of resource-exhaustion problem, but I doubt that it's just
> the number of backends that's at issue, except indirectly. (He could
> be running out of swap space or filetable slots, possibly.)
>
> regards, tom lane
>
> ************

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-12-16 19:58:40 Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Previous Message Keith Parks 1999-12-16 19:24:35 Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock