Skip site navigation (1) Skip section navigation (2)

Re: per user/database connections limit again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Petr Jelinek <pjmodos(at)parba(dot)cz>,Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: per user/database connections limit again
Date: 2005-07-31 01:01:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I have "worked over" your patch and I think it is ready for application.

I've made another pass over this and should be able to commit tomorrow
(I'm about to knock off for today, and ran out of time to test
pg_dumpall).  One thing I changed was that it didn't make sense to me
for CREATE DATABASE to copy the template database's datconnlimit.
We don't copy its datallowconn or datconfig, so why datconnlimit?

BTW I disagree with removing datallowconn; that is different from
datconnlimit = 0 because it is enforced even against superusers.
(Similar remarks apply for rolcanlogin vs rolconnlimit.)

			regards, tom lane

Attachment: connlimit.patch.gz
Description: application/octet-stream (15.2 KB)

In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-07-31 02:36:05
Subject: Re: PL/PGSQL: Dynamic Record Introspection
Previous:From: David FetterDate: 2005-07-31 00:34:58
Subject: Re: [HACKERS] PL/Perl list value return causes segfault

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group