Re: [HACKERS] Query to help in debugging
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: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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 http://wiki.postgresql.org/wiki/Guide_to_reporting_problems#Things_you_need_to_mention_in_problem_reports Feel free to make any adjustments you feel are needed. :-) Oh, so we already have it documnted. Great. I adjusted it slightly to be clearer. -- Bruce Momjian br...@momjian.ushttp://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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, 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 having to adjust the exclusion list for different versions is
easily worth that. I think the source column is potentially useful when
we're casting this type of fishing net, too.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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 having to adjust the exclusion list for different versions is
easily worth that. I think the source column is potentially useful when
we're casting this type of fishing net, too.
Done.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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 would print a few not-all-that-interesting settings made by initdb,
but not having to adjust the exclusion list for different versions is
easily worth that. I think the source column is potentially useful when
we're casting this type of fishing net, too.
Done.
Here is my very wide output:
name|
current_setting|source
+--+--
version| PostgreSQL 9.3devel on
x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.4.5-8) 4.4.5, 64-.|
version()
|.bit
|
application_name | psql
| client
client_encoding| UTF8
| client
DateStyle | ISO, MDY
| configuration file
default_text_search_config | pg_catalog.english
| configuration file
lc_messages| en_US.UTF-8
| configuration file
lc_monetary| en_US.UTF-8
| configuration file
lc_numeric | en_US.UTF-8
| configuration file
lc_time| en_US.UTF-8
| configuration file
log_timezone | US/Eastern
| configuration file
max_connections| 100
| configuration file
max_stack_depth| 2MB
| environment variable
shared_buffers | 128MB
| configuration file
TimeZone | US/Eastern
| configuration file
Is there an easy way to wrap the 'version' value to a 40-character width?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query to help in debugging
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 this? It could
just as easily be a different query.
I am fine with that:
SELECT version();
SELECT name, current_setting(name), source
FROMpg_settings
WHERE source NOT IN ('default', 'override');
Output:
test= SELECT version();
version
-
PostgreSQL 9.3devel on x86_64-unknown-linux-gnu, compiled by gcc
(Debian 4.4.5-8) 4.4.5, 64-bit
(1 row)
test= SELECT name, current_setting(name), source
test- FROMpg_settings
test- WHERE source NOT IN ('default', 'override');
name| current_setting |source
++--
application_name | psql | client
client_encoding| UTF8 | client
DateStyle | ISO, MDY | configuration file
default_text_search_config | pg_catalog.english | configuration file
lc_messages| en_US.UTF-8| configuration file
lc_monetary| en_US.UTF-8| configuration file
lc_numeric | en_US.UTF-8| configuration file
lc_time| en_US.UTF-8| configuration file
log_timezone | US/Eastern | configuration file
max_connections| 100| configuration file
max_stack_depth| 2MB| environment variable
shared_buffers | 128MB | configuration file
TimeZone | US/Eastern | configuration file
(13 rows)
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
