Andreas Pflug wrote: > Bruce Momjian wrote: > > Dave Page wrote: > > >>The problem is, pg_hba.conf might be editted via the OS unlike the text > >>version of pg_shadow which is only editted via the server, which would > >>make appropriate locking nigh-on impossible afaics. > >> > >>Unless you're advocating only allowing pg_hba modifications via the > >>server, in which case it must be started in default configuration before > >>any mods can be made. That doesn't seem like a good idea to me :-( > > > > > > I am thinking we will need load_pg_hba() and write_pg_hba() that will > > load and write the table to pg_hba.conf. > > Isn't the pg_hba.conf situation quite the same as postgresql.conf? The > GUCs with pg_settings is the GUC like a table, but with comments that > exceed config_generic.long_desc.
Well, pg_hba.conf is ordered, which is different, and it more of a columnar values that postgresql.conf. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (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 2: Don't 'kill -9' the postmaster
