| From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remote administration functionality |
| Date: | 2005-08-01 14:15:33 |
| Message-ID: | m2u0i9oi9m.fsf@Douglas-McNaughts-Powerbook.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
>
>
>> -----Original Message-----
>> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
>> I am thinking we will need load_pg_hba() and write_pg_hba() that will
>> load and write the table to pg_hba.conf.
>
> Yeah, that bit is straghtforward enough, but what about the situation
> where dba #1 updates the pg_hba table, at the same time as dba #2 is
> editting pg_hba.conf in vi?
"Don't do that then."
With this change, editing ph_hba.conf by hand should only be done when
the database is down...
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-01 14:15:51 | Re: Remote administration functionality |
| Previous Message | Alvaro Herrera | 2005-08-01 14:12:06 | Re: Remote administration functionality |