On Thu, Jun 23, 2005 at 12:44:25AM -0400, Tom Lane wrote: > I wrote: > > ... because it's written to not loop more than > > superuser_reserved_connections times, and it's hard to imagine anyone > > would set that to more than half a dozen or so. > > We could help keep people on the correct path if guc.c enforced a sane > upper limit on superuser_reserved_connections. I'm thinking somewhere > around 10. > > Any thoughts about that?
Maybe a warning in the docs and the sample/default config file would be better. It seems silly to limit this just because it might cause a performance problem (this is just a performance issue, right?) -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
