Re: Query to help in debugging

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: bricklen <bricklen(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Query to help in debugging
Date: 2013-01-19 16:46:27
Message-ID: 25570.1358613987@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dimitri Fontaine 2013-01-19 17:05:02 Re: Passing connection string to pg_basebackup
Previous Message Tom Lane 2013-01-19 16:27:28 Re: BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-01-19 16:57:12 Re: Contrib PROGRAM problem
Previous Message Bruce Momjian 2013-01-19 16:43:36 Re: Query to help in debugging