> > > > 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.

Doing it from psql is the part I fail to see a real use-case for. The
people who would use psql for it would probably just use vi or emacs or
sed or whatever on the file itself.
If you needed to do it remotely, you could just call pqsl once to get
the data out to a local file, edit that file, and then call it again to
put it back on the server, no?

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Magnus Hagander wrote:
>
> > > > > 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.
>
> Doing it from psql is the part I fail to see a real use-case for. The
> people who would use psql for it would probably just use vi or emacs or
> sed or whatever on the file itself.
> If you needed to do it remotely, you could just call pqsl once to get
> the data out to a local file, edit that file, and then call it again to
> put it back on the server, no?

I don't think the proposed read/write API would allow client-side files
to be written to the server, or at least I didn't see that API in there.

--
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