| From: | heikki(at)postgresql(dot)org (Heikki Linnakangas) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Check that connection limit is within valid range. |
| Date: | 2009-01-30 17:24:47 |
| Message-ID: | 20090130172447.B0A487559ED@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Check that connection limit is within valid range. IOW, not < -1.
It's missing in older versions too, but it doesn't seem worth
back-porting. All negative are just harmlessly treated as "no limit", and
tightening the check might even brake an application that relies on it.
Modified Files:
--------------
pgsql/src/backend/commands:
dbcommands.c (r1.218 -> r1.219)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.218&r2=1.219)
user.c (r1.185 -> r1.186)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/user.c?r1=1.185&r2=1.186)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Mkz | 2009-01-30 19:42:03 | pgbouncer - pgbouncer: win32: improve service description Hiroshi Saito |
| Previous Message | Tom Lane | 2009-01-30 16:59:16 | pgsql: Defend against null input in analyze_requires_snapshot(), per |