Re: Per database connection limit buglet - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: Per database connection limit buglet
Date
Msg-id 497DABDD.40906@enterprisedb.com
Whole thread Raw
In response to Per database connection limit buglet  ("Dave Page" <dpage@pgadmin.org>)
Responses Re: Per database connection limit buglet  (Dave Page <dpage@pgadmin.org>)
Re: Per database connection limit buglet  (tomas@tuxteam.de)
Re: Per database connection limit buglet  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Per database connection limit buglet  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Dave Page wrote:
> It's possible to set a per-database connection limit of < -1, which seems bogus:

Yeah. That's simple to fix, but I'm having trouble wordsmithing the
error message. This is what I came up with:

invalid connection limit %d (must be -1, meaning no limit, or greater)

Any better suggestions?

I also note that you can set it to INT_MAX, while max_connections is
limited to INT_MAX/4, but I'm inclined to leave that alone.

> 8.3 seems similarly afflicted - I haven't tested any further back.

Hmm, I don't think this should be backported, since it doesn't cause any
  actual problems. We'd just risk breaking people's scripts that use
-999 to mean "no limit". (they will be broken when they upgrade to 8.4
anyway, of course, but that's fine)

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Dave Page
Date:
Subject: Re: BUG #4628: services doesn't start
Next
From: Dave Page
Date:
Subject: Re: Per database connection limit buglet