| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| 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 05:04:55 |
| Message-ID: | 200210260504.g9Q54t519896@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
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 | Bruno Wolff III | 2002-10-26 05:26:39 | Re: idle connection timeout ... |
| Previous Message | Robert Treat | 2002-10-26 05:01:47 | Re: idle connection timeout ... |