Magnus Hagander wrote: > > > The difference is that if the other admin edited it in vi > > *last week* > > > it will still break with your way, unless every admin > > always rembers > > > to do > > > load_pg_hba() before doing *anything at all*. > > > > Yes, good point. In thinking about this, I think we are > > better having the load() function load the file into a > > temporary table, which can then be modified and flushed down > > to the flat file. Another option is that queries to the > > table automatically read the flat file, but that might force > > writes to the file on first update, so that might be bad. > > That would be very bad. You can only flush at controlled times.
Right. > > > I fail to see how this is better than just editing the > > file. Because > > > it basically *is* a file editing function limited to pg_hba.conf. > > > Perhaps what we need is a file reader/writer that is > > hardcoded to the > > > pg_hba.conf file? > > > > It allows remote administration, and by using columns for the > > pg_hba.conf lines (except for comments), we are making it > > somewhat easier. > > I fail to see a real use-case for somebody editing pg_hba.conf *by hand* > using this. I can see it happening through a tool like phppgadmin or > pgadmin, in which case this will actually make it *harder* to implement. Uh, not sure why it would be harder. What system would be easier? Sure, file I/O works, but you can't even try to do that from psql. -- 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 4: Have you searched our list archives? http://archives.postgresql.org
