Re: exposing pg_controldata and pg_config as functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: exposing pg_controldata and pg_config as functions
Date
Msg-id 56C4EA37.7050009@gmx.net
Whole thread Raw
In response to Re: exposing pg_controldata and pg_config as functions  (Joe Conway <mail@joeconway.com>)
Responses Re: exposing pg_controldata and pg_config as functions
List pgsql-hackers
On 2/17/16 12:15 PM, Joe Conway wrote:
> On 02/17/2016 02:32 AM, Michael Paquier wrote:
>> Actually, having second-thoughts on the matter, why is is that
>> necessary to document the function pg_config()? The functions wrapping
>> a system view just have the view documented, take for example
>> pg_show_all_file_settings, pg_show_all_settings,
>> pg_stat_get_wal_receiver, etc.
> 
> Ok, removed the documentation on the function pg_config() and pushed.

I still have my serious doubts about this, especially not even requiring
superuser access for this information.  Could someone explain why we
need this?




pgsql-hackers by date:

Previous
From: "Constantin S. Pan"
Date:
Subject: Re: [WIP] speeding up GIN build with parallel workers
Next
From: Gavin Flower
Date:
Subject: Re: Figures in docs