From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Problem with reloading groups in pg_hba.conf |
Date: | 2002-03-21 17:02:13 |
Message-ID: | 28077.1016730133@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> 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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2002-03-21 17:02:28 | Re: Domain Support -- another round |
Previous Message | Bruce Momjian | 2002-03-21 16:52:04 | Re: Problem with reloading groups in pg_hba.conf |