Making pg_config and pg_controldata output available via SQL

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Making pg_config and pg_controldata output available via SQL
Date: 2010-02-03 19:13:31
Message-ID: 4b69caeb.9513f30a.731a.3427@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'd really like to see the data from pg_config and pg_controldata available
through SQL, such as by adding output to pg_show_all_settings(), or adding new
SRFs named something like pg_config() and pg_controldata(). Does this make as
much sense to the rest of the world as it does to me? In particular it's
useful to be able to find $libdir without requiring pg_config, as some
packagers tend not to include it in anything put the -dev packages, but all
those settings seem useful to have on hand, and in at least most cases
shouldn't be tough to expose via SQL. Comments?

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2010-02-03 19:13:43 Re: PG 9.0 and standard_conforming_strings
Previous Message Tom Lane 2010-02-03 19:04:47 Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]