Tom Lane wrote:
Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes:
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:
Why does it need to be anything except GUC's standard "invalid value"
message? I really don't believe that this case is worth making
translators deal with an additional string.
I guess. The message in guc.c seems a bit cumbersome, though, so I did
create a new message for it. It's now simply "invalid connection limit: %d".
The check was missing from per-user connection limits, fixed that too.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
