| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| 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-14 20:40:14 |
| Message-ID: | 55F730AE.3060209@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/8/15 4:56 PM, Andrew Dunstan wrote:
> The problem is that at least this user's system had something odd about
> it. so that I wouldn't entirely trust the output of
>
> select is_supported
> from information_schema.sql_features
> where feature_name = 'XML type';
>
> to reflect the config.
This should be a built-in function, not dependent on the state of the
catalogs, like pg_build_option('xml') returns boolean.
> I also have cases where clients don't want to give me superuser access,
> and sometimes not even shell access, and it could well be useful to me
> to be able to say to them "OK, you need to make sure that this file in
> this location has this entry".
Not sure what this has to do with this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2015-09-14 20:47:31 | Re: Can extension build own SGML document? |
| Previous Message | Teodor Sigaev | 2015-09-14 20:31:59 | Re: Review: GiST support for UUIDs |