From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
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 14:01:37 |
Message-ID: | 200508011401.j71E1cs00299@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
>
>
> > -----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?
I don't see any way to fix that. The hope is that the administrator has
enough control that this isn't happenening --- it could already happen
now if who people edit the same file with different editors/locking
systems.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-08-01 14:02:41 | Re: Remote administration functionality |
Previous Message | Alvaro Herrera | 2005-08-01 13:14:24 | Re: [HACKERS] Autovacuum loose ends |