Re: exposing pg_controldata and pg_config as functions

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-08 20:21:12
Message-ID: 55EF4338.6050302@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/7/15 7:32 PM, Alvaro Herrera wrote:
> Andrew Dunstan wrote:
>
>> I already gave a use case that you dismissed in favour of a vague solution
>> that we don't actually have. You seem to be the only person objecting to
>> this proposal.
>
> I think that use case would be better served by a completely different
> interface -- some way to query the server, "does this installation
> support feature X?" What you proposed, using a regexp to look for
> --enable-xml in the pg_config --configure output, doesn't look all that
> nice to me.

Agreed.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-09-08 20:22:03 Re: exposing pg_controldata and pg_config as functions
Previous Message Robert Haas 2015-09-08 20:18:12 Re: Hooking at standard_join_search (Was: Re: Foreign join pushdown vs EvalPlanQual)