Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Yes, that was the issue. We tell people pg_hba.conf only gets reloaded > > when they tell the postmaster to do it. We can't have it happening at > > random times, e.g. password change. > > I agree on that: the signal should cause the postmaster to reload > pg_pwd/pg_group info *only*. So you cannot integrate the data from > these files into the same datastructure as you use for pg_hba.conf; > they have to be separate datastructures. > > I think what you are really asking is whether to expand groups by > substitution of user names during read of the file, vs doing it > on-the-fly when accepting a connection. On that I agree with Ross: > better to move work out of the connection logic and into the file > reread logic as much as possible.
Yes, I am doing that. pg_group will be tokenized into username tokens, and on connection, the mention of a group token in pg_hba.conf will cause a spin through the pg_group tokens to find a matching groupname, then it will look for the requested username. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
