On Friday 25 October 2002 07:03 pm, Bruce Momjian wrote:
> Tom Lane wrote:
> > Robert Treat <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to