From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remote administration functionality |
Date: | 2005-08-01 14:18:25 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C77F5@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
> > 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.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-08-01 14:22:11 | Re: Remote administration functionality |
Previous Message | Andreas Pflug | 2005-08-01 14:17:37 | Re: Remote administration functionality |