| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Mike Mascari <mascarm(at)mascari(dot)com>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: idle connection timeout ... |
| Date: | 2002-10-25 23:03:59 |
| Message-ID: | 200210252303.g9PN3x319316@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > On Fri, 2002-10-25 at 16:17, Tom Lane wrote:
> >> I prefer GUC variables to table entries for setting stuff like recursion
> >> limits; they're much lighter-weight to create and access, and you don't
> >> need an initdb to add or remove a parameter.
>
> > I don't see an adequate way to store the individual settings as GUC
> > variables per user...
>
> Have you looked at the per-database and per-user GUC facilities in 7.3?
Nice idea. You can now have per-user/db settings that are SET when the
connection is made. You can set any GUC variable that way. We just
need a variable that can look at all sessions and determine if that user
has exceeded their connection quota.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-25 23:10:23 | Re: Time for RC1 soon? |
| Previous Message | Tom Lane | 2002-10-25 21:06:39 | Re: Time for RC1 soon? |