| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Luke Lonergan <llonergan(at)greenplum(dot)com>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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-08-01 04:28:55 |
| Message-ID: | 24486.1122870535@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Luke Lonergan wrote:
>> 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.
Remote reboot to change shared_buffers and other shmem-sizing parameters
seems pretty doable: all you need is a slightly more user-friendly
version of the standard response to backend crash, since that sequence
already kills and recreates the shmem segment. The postmaster itself
doesn't have to change anything.
I'm not sure how to handle remote reconfiguration of, say,
listen_addresses. The postmaster doesn't normally reconsider that after
postmaster startup. We'd have to either fix that (difficulty uncertain)
or invent a way for the postmaster to quit and restart (ick).
None of this seems like 8.1 material, though. May I remind you that
we're already a month past feature freeze?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-08-01 07:41:19 | Re: Remote administration functionality |
| Previous Message | Andrew - Supernews | 2005-08-01 04:17:38 | Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive |