| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-26 05:01:47 |
| Message-ID: | 200210260101.47224.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 25 October 2002 07:03 pm, Bruce Momjian wrote:
> 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?
>
Maybe I haven't looked at them enough ;-)
> 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.
I understand how you are able to set those variables per db, but I don't see
how you can get those settings to persist between database shutdowns.
Perhaps someone can point me to the relevant documentation?
Robert Treat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-26 05:04:55 | Re: idle connection timeout ... |
| Previous Message | Bruce Momjian | 2002-10-26 02:17:22 | Request for supported platforms |