Re: [HACKERS] A configure.in patch check (fwd)

2002-08-25 Thread Tom Lane
"Nigel J. Andrews" <[EMAIL PROTECTED]> 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 config

Re: [HACKERS] A configure.in patch check (fwd)

2002-08-25 Thread Nigel J. Andrews
On Sun, 25 Aug 2002, Tom Lane wrote: > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes: > > + AC_MSG_CHECKING([for default superuser reserved number of connections]) > > + PGAC_ARG_REQ(with, reservedbackends, [ --with-reservedbackends=Nset default >superuser reserved number of connections [2]

Re: [HACKERS] A configure.in patch check (fwd)

2002-08-25 Thread Tom Lane
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes: > + AC_MSG_CHECKING([for default superuser reserved number of connections]) > + PGAC_ARG_REQ(with, reservedbackends, [ --with-reservedbackends=Nset default >superuser reserved number of connections [2]], > + [], > + [wi

[HACKERS] A configure.in patch check (fwd)

2002-08-25 Thread Nigel J. Andrews
Helps if I attach the patch... -- Forwarded message -- Date: Sun, 25 Aug 2002 14:36:19 +0100 (BST) From: Nigel J. Andrews <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: A configure.in patch check Would someone apply the attached patch to the development source and let me