Re: Remote administration functionality
- From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- To: Luke Lonergan <llonergan(at)greenplum(dot)com>
- Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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>, Garry Coombe <gcoombe(at)greenplum(dot)com>
- Subject: Re: Remote administration functionality
- Date: Sun, 31 Jul 2005 20:33:32 -0400 (EDT)
- Message-id: <200508010033.j710XWS16954@candle.pha.pa.us> <text/plain>
Luke Lonergan wrote:
> Bruce,
>
> On 7/31/05 6:58 AM, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
>
> > TODO has:
> >
> > o Allow pg_hba.conf settings to be controlled via SQL
> >
> > This would require a new global table that is dumped to flat file
> > for
> > use by the postmaster. We do a similar thing for pg_shadow
> > currently.
> >
> > I was thinking of a global table that can be modified with
> > INSERT/UPDATE/DELETE and is then dumped to a flat file, like we do with
> > pg_shadow. For changing the file, I think we would need a sequence
> > number for each row. In fact, perhaps it should act like a float, so if
> > you insert row sequence number 2.5, it goes between rows 2 and 3, and
> > then the rows are renumbered, perhaps automatically. This is how APL
> > programming used to work, if I remember correctly.
>
> This sounds great.
>
> Has there been any agreement or a concept for remote reboot?
Reload of config file and rotate log files were part of the original
patch that I will try to apply. I am not sure how remote restart would
work.
--
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
Home |
Main Index |
Thread Index