| 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: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: For review: Server instrumentation patch |
| Date: | 2005-07-25 15:17:44 |
| Message-ID: | 27911.1122304664@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:
> Andrew Dunstan wrote:
>> It also just strikes me as just the wrong way to go about solving the
>> apparent problem.
> I thought an API for postgresql.conf is what we agreed to, but I don't
> see it on the TODO list. Is that correct?
Like you, I seem to recall some prior discussion along this line, but
I think it didn't get solid enough to produce a TODO item. Right now
the best we could do is
* Better support for remote database administration, eg, APIs
to change configuration and restart the postmaster
which is mighty vague.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-25 15:26:52 | Re: For review: Server instrumentation patch |
| Previous Message | Bruce Momjian | 2005-07-25 15:16:42 | Re: regression failure on stats test |