| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 06:04:15 |
| Message-ID: | 200210260204.15799.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Saturday 26 October 2002 01:04 am, Bruce Momjian wrote:
> Robert Treat wrote:
> > > 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?
>
> The per db/user stuff is stored in the pg_database/pg_shadow tables per
> row, so they exist in permanent storage.
Ah.. that was the missing link. I don't think the docs mention anything about
the information being stored in pg_database or pg_shadow, they always refer
to the "session default" which made me wonder what happened "between
sessions". Perhaps someone (me?) should work up a patch to help clarify
this....
Robert Treat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-26 14:18:08 | Re: Request for supported platforms |
| Previous Message | Bruno Wolff III | 2002-10-26 05:26:39 | Re: idle connection timeout ... |