| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "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 07:41:19 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9640@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: 01 August 2005 01:35
> To: Dave Page
> Cc: Tom Lane; Magnus Hagander; PostgreSQL-development
> Subject: Re: [HACKERS] Remote administration functionality
>
> 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?
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paesold | 2005-08-01 07:55:11 | Re: [HACKERS] Autovacuum loose ends |
| Previous Message | Tom Lane | 2005-08-01 04:28:55 | Re: Remote administration functionality |