From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: exposing pg_controldata and pg_config as functions |
Date: | 2015-09-01 01:47:51 |
Message-ID: | 55E503C7.8050300@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/25/15 11:32 PM, Joe Conway wrote:
> 1.) pg_controldata() function and pg_controldata view added
I don't think dumping out whatever pg_controldata happens to print as a
bunch of text fields is very sophisticated. We have functionality to
compute with WAL positions, for example, and they won't be of much use
if this is going to be all text.
Also, the GUC settings tracked in pg_control can already be viewed using
normal mechanisms, so we don't need a second way to see them.
The fact that some of this is stored in pg_control and some is not is
really an implementation detail. We should be thinking of ways to
expose specific useful information in useful ways, not just dump out
everything we can find. Ultimately, I think we would like to move away
from people parsing textual pg_controldata output, but this proposal is
not moving very far in that direction.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-09-01 02:23:58 | Re: Horizontal scalability/sharding |
Previous Message | Peter Eisentraut | 2015-09-01 01:38:29 | Re: exposing pg_controldata and pg_config as functions |