Re: [HACKERS] Update on my 6.4.2 progress

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wayne Piekarski <wayne(at)senet(dot)com(dot)au>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Update on my 6.4.2 progress
Date: 1999-06-19 18:17:40
Message-ID: 11610.929816260@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> The 6.4.2 code would not allocate all shared memory/semaphores at
> startup, and only fail when you go to a large number of backends. 6.5
> fixes this by allocating it all on startup.

Also, I don't think 6.4.* actually tested for an attempt to start one
too many backends; it'd just do it and eventually you'd get a failure
downstream somewhere. (A failure *will* happen, because there are
fixed-size arrays containing per-backend entries, but I think the code
failed to notice ...)

There is now code in the postmaster that prevents starting that fatal
65th (or whatever) backend. If you want to keep running 6.4.2 you
should consider adopting CountChildren() and the code that calls it
from 6.5's src/backend/postmaster/postmaster.c.

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Adam Haberlach 1999-06-19 18:49:03 Re: [HACKERS] BeOS port
Previous Message Cyril VELTER 1999-06-19 13:32:26 Re: [HACKERS] BeOS port