| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Per database connection limit buglet |
| Date: | 2009-01-26 12:51:12 |
| Message-ID: | 937d27e10901260451l18531451wb2d6c0d142b69536@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jan 26, 2009 at 12:26 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 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?
Perhaps drop the 'meaning no limit'? Less helpful perhaps (but that's
what the manual is for), but it sounds better
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tomas | 2009-01-26 13:09:43 | Re: Per database connection limit buglet |
| Previous Message | Heikki Linnakangas | 2009-01-26 12:26:05 | Re: Per database connection limit buglet |