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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
