Re: exposing pg_controldata and pg_config as functions
От | Joe Conway |
---|---|
Тема | Re: exposing pg_controldata and pg_config as functions |
Дата | |
Msg-id | 55D8FCA4.209@joeconway.com обсуждение исходный текст |
Ответ на | Re: exposing pg_controldata and pg_config as functions (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: exposing pg_controldata and pg_config as functions
|
Список | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/20/2015 07:54 AM, Joe Conway wrote: > On 08/20/2015 06:59 AM, Andrew Dunstan wrote: >> I was a bit interested in pg_config information, for this reason: >> I had a report of someone who had configured using --with-libxml >> but the xml tests actually returned the results that are expected >> without xml being configured. The regression tests thus passed, >> but should not have. It occurred to me that if we had a test >> like > >> select pg_config('configure') ~ '--with-libxml' as has_xml; > >> in the xml tests then this failure mode would be detected. > > I've found use for them both in the past. A fair amount of bit-rot > has set it no doubt, and these were quick and dirty to begin with, > but I have these hacks from a while back: > > https://github.com/jconway/pg_config The attached implements pg_config as a backend SRF and a matching system view. A few notes: 1) The syntax is a bit different than what Andrew proposed: 8<---------------- select setting ~ '--with-libxml' as has_xml from pg_config where name = 'CONFIGURE'; has_xml - --------- t (1 row) 8<---------------- In particular note that the name values are all upper case to be consistent with pg_config, and at least currently there is no version of the function which accepts a name as an argument (didn't seem worthwhile to me). 2) No docs or related regression test yet. I will do that if there is enough interest in this getting committed. So far no one except Andrew and I have chimed in. 3) Requires a catalog version bump (not in posted diff) 4) The static function cleanup_path() was borrowed from src/bin/pg_config/pg_config.c It is a small and stable function (no change since 2010 AFAICS), so maybe not worth the effort, but I was wondering if it should be moved to src/common somewhere and shared. I will add this to the next commitfest. Comments/feedback encouraged. Joe - -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJV2PykAAoJEDfy90M199hlQW0P/1fLCtFe50wFanleOxo41aki yR8uG5vUZCLosx7lYd4+LyeE2g+bfs+fK6XgL1qIafI0zyxQSAU8TtjsIPQjjsvU rNn1MWRrlOLEfOMMzbJPo01w5wzLhBvFzrYQ8vVtvf+T2PzjbU1hTMOcmaeXv6If jYv0KQDgPBk/VPZ0D7MI4nYXVzNSInDLD7TGEpoTQwZ0oqvZwScSXc933isoULB4 4isael+g6mQJNoPz+OQEhUSoC922mrGs12SarfHJiUqJs1/NleClRRZ/9llCBnb2 3+zW6cb4XNh8aVP33zTtCsbrio206VjumWUYMNs546+qChormBOnYtZiIVRNRnPk z4x/vxuhXVndDp1VnE5V5mRiW3B8ABliBf1Bcnf/Z+Gxi84LaZVtmL2hJrmn7voT EZsQn/gmpB6ThHKbOl3t060fGZ/RAPDUwOWoYUIVcohOQqxK/iIka0bFM5cnuXO0 8oJ7CFkPSW7kBPs3uPO4Psf/jzrfaK3b/ZfitoV77sMQiVCABlR3a8khw+cPBrok av/1afnGfz6qSxsV8sAyKUmRZkLDtmT01GUHCuujof1PQ3tD8zVsQWI3r51UcGB3 tFKvvy9koTHEunqkU6yQrCWNOEzHpGXEa1RIV33Ywgh0deKVEU5EbfJF5iIHBgOy dYf2PHbYW7F1RSqKnZIa =A2+X -----END PGP SIGNATURE-----
Вложения
В списке pgsql-hackers по дате отправления: