| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | 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-17 21:46:31 |
| Message-ID: | 56C4EA37.7050009@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Raiskup | 2016-02-17 21:47:04 | Re: [HACKERS] Packaging of postgresql-jdbc |
| Previous Message | Constantin S. Pan | 2016-02-17 21:46:04 | Re: [WIP] speeding up GIN build with parallel workers |