We already pre-allocate all shared memory and resources on postmaster


Hans-Jürgen Schönig wrote:
> There is a problem which occurs from time to time and which is a bit 
> nasty in business environments.
> When the shared memory is eaten up by some application such as Apache 
> PostgreSQL will refuse to do what it should do because there is no 
> memory around. To many people this looks like a problem relatd to 
> stability. Also, it influences availability of the database itself.
> I was thinking of a solution which might help to get around this problem:
> If we had a flag to tell PostgreSQL that XXX Megs of shared memory 
> should be preallocated by PostgreSQL. The database would the sure that 
> there is always enough memory around. The problem is that PostgreSQL had 
> to care more about memory consumption.
> Of course, the best solution is to put PostgreSQL on a separate machine 
> but many people don't do it so we have to live with memory leaks caused 
> by other software (we have just seen a nasty one in mod_perl).
> Does it make sense?
>       Regards,
>               Hans
> -- 
> Cybertec Geschwinde u Schoenig
> Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria
> Tel: +43/2952/30706; +43/664/233 90 75
> www.cybertec.at, www.postgresql.at, kernel.cybertec.at
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> http://www.postgresql.org/docs/faqs/FAQ.html

  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?


Reply via email to