Re: A configure.in patch check (fwd)

"Nigel J. Andrews" <nandrews@investsystems.co.uk> writes:
> It is a GUC. It's exactly like max_backends. I took the easy route out and
> just followed where DEF_MAXBACKENDS was being set rather than hard wiring
> the value any where.

Oh.  Well, skip the configure part: the only reason there's still a
configure parameter for maxbackends is backwards compatibility with
ancient configure scripts (from days when it was in fact frozen at
configure time).  I don't see a need to provide one for reserved_slots.

> Rather distressingly in order to get this new value into where it's needed
> I had to hit quite a few files, more than I would have expected. Again I
> just followed how MaxBackends was being sent to where it was needed but is
> there any particular reason why storage/ipc/sinvaladt.c:SIBackendInit()
> can't access MaxBackends and my new ReservedBackends directly?

Probably not.  Again, the way that MaxBackends is handled is largely
legacy code.  You'd have been better off looking at almost any other
GUC parameter as a template ;-)
        regards, tom lane