| From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "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>, "Garry Coombe" <gcoombe(at)greenplum(dot)com> |
| Subject: | Re: Remote administration functionality |
| Date: | 2005-07-31 15:49:34 |
| Message-ID: | BF12411E.A5A1%llonergan@greenplum.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
- Luke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-07-31 16:02:51 | Re: Remote administration functionality |
| Previous Message | Bruce Momjian | 2005-07-31 13:58:09 | Re: Remote administration functionality |