Bruce Momjian wrote:
Why are you insisting on cramming version() into this? It could
just as easily be a different query.
I am fine with that:
Done.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Sat, Jan 19, 2013 at 11:20:19AM -0500, Kevin Grittner wrote:
Bruce Momjian wrote:
I am wondering if we should make this query more widely used, perhaps by
putting it in our docs about reporting bugs, or on our website.
http://wiki.postgresql.org/wiki/Server_Configuration
Bruce Momjian br...@momjian.us writes:
I am wondering if we should make this query more widely used, perhaps by
putting it in our docs about reporting bugs, or on our website.
I find the manual exclusion list to be poor style, and not at all
future-proof. Maybe we could use
select name,
Tom Lane wrote:
I find the manual exclusion list to be poor style, and not at all
future-proof. Maybe we could use
select name, setting, source from pg_settings
where source not in ('default', 'override');
This would print a few not-all-that-interesting settings made by initdb,
but not
On Sat, Jan 19, 2013 at 12:58:35PM -0500, Kevin Grittner wrote:
Tom Lane wrote:
I find the manual exclusion list to be poor style, and not at all
future-proof. Maybe we could use
select name, setting, source from pg_settings
where source not in ('default', 'override');
This
Bruce Momjian br...@momjian.us writes:
Tom Lane wrote:
select name, setting, source from pg_settings
where source not in ('default', 'override');
Here is my very wide output:
Why are you insisting on cramming version() into this? It could
just as easily be a different query.
On Sat, Jan 19, 2013 at 03:29:36PM -0500, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Tom Lane wrote:
select name, setting, source from pg_settings
where source not in ('default', 'override');
Here is my very wide output:
Why are you insisting on cramming version() into
