Re: Hardwired MAXBACKENDS limit could be history - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Hardwired MAXBACKENDS limit could be history
Date
Msg-id 200101270443.XAA04101@candle.pha.pa.us
Whole thread Raw
In response to Hardwired MAXBACKENDS limit could be history  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> It would require only very minor changes in the main backend code to
> eliminate entirely the hard-wired upper bound MAXBACKENDS.  This would
> be nice since there'd never be any need to recompile in order to
> increase the soft limit MaxBackends (-N).  However I see that the
> SysV-semaphore emulation code used by the QNX and Darwin ports still
> makes use of MAXBACKENDS to size some arrays.  I don't especially want
> to touch that code, since I am in no position to test it.  Perhaps
> someone who uses QNX and/or Darwin would like to tweak the sema code
> to not depend on a compile-time-constant MAXBACKENDS?
> 
> I'm not thinking about getting this done in time for 7.1, but I think
> it'd be a nice cleanup for 7.2.
> 
> Bruce, a TODO item please:
>   * Remove compile-time upper limit on number of backends (MAXBACKENDS)

Added to TODO.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: Bug in FOREIGN KEY
Next
From: Bruce Momjian
Date:
Subject: Re: Sure enough, the lock file is gone