| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Josh berkus <josh(at)agliodbs(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: exposing pg_controldata and pg_config as functions |
| Date: | 2016-02-18 02:08:51 |
| Message-ID: | CAB7nPqQxR6TEGpDcDF0qEG-aHdgo9q=yTxbtD0KfuZni=7RaUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 18, 2016 at 11:02 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 2/17/16 5:20 PM, Josh berkus wrote:
>> I have a use-case for this feature, at part of it containerized
>> PostgreSQL. Right now, there is certain diagnostic information (like
>> timeline) which is exposed ONLY in pg_controldata.
>
> I'm talking about the pg_config() function, not pg_controldata.
Andrew has mentioned a use case he had at the beginning of this thread
to enhance a bit the regression tests related to libxml.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-02-18 02:15:56 | Re: Figures in docs |
| Previous Message | Peter Eisentraut | 2016-02-18 02:02:11 | Re: exposing pg_controldata and pg_config as functions |