On 02/18/2016 12:30 AM, Andres Freund wrote: > On 2016-02-17 21:19:08 -0500, Peter Eisentraut wrote: >> On 2/17/16 9:08 PM, Michael Paquier wrote: >>> On Thu, Feb 18, 2016 at 11:02 AM, Peter Eisentraut <pete...@gmx.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. >> >> While that idea was useful, I think we had concluded that there are >> better ways to do this and that this way probably wouldn't even work >> (Windows?).
Just to be clear, AFAIK there is no issue with the committed changes on Windows. If there is please provide a concrete example that we can discuss. > I don't understand why you're so opposed to this. Several people said > that they're interested in this information in the current discussion > and it has been requested repeatedly over the years. For superusers you > can already hack access, but it's darn ugly. Exactly. -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
Description: OpenPGP digital signature