Bug report form: locale/encoding
Considering the amount of bug repotrs that get their first question as
"what's the locale" and "what's the encoding", should we perhaps add
those fields to the bug reporting form?
And if we should, should we add them as optional or mandatory?
//Magnus
On Thu, Mar 16, 2006 at 10:11:23AM +0100, Magnus Hagander wrote:
Considering the amount of bug repotrs that get their first question as
"what's the locale" and "what's the encoding", should we perhaps add
those fields to the bug reporting form?And if we should, should we add them as optional or mandatory?
Mandatory, including a quick description on how to get the values.
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:
$ pg_buginfo <dbname>
Platform: blah
Version: blah
Compiler: blah
etc...
FrozenXID: blah
Encoding: blah
Locale: blah
Which could then be cut and paste into an email or the bug form. Maybe
with optional table name it would provide more info about just that
table. Or if you provide a query it generates explain output.
Obviously it won't work in situations where the system is completely
broken.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
Show quoted text
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
tool for doing 5% of the work and then sitting around waiting for someone
else to do the other 95% so you can sue them.
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:
It sounds good. Should we setup a bug tracker system for pgsql?
Regards,
William ZHANG
William ZHANG wrote:
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:It sounds good. Should we setup a bug tracker system for pgsql?
Please start by reviewing previous discussions on this point. We really
don't need to have this discussion every few months.
cheers
andrew
Martijn van Oosterhout <kleptog@svana.org> writes:
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:
pg_config and pg_controldata together cover most if not all of this
info, and neither requires a running postmaster.
regards, tom lane
On Thu, Mar 16, 2006 at 10:07:52AM -0500, Tom Lane wrote:
Martijn van Oosterhout <kleptog@svana.org> writes:
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:pg_config and pg_controldata together cover most if not all of this
info, and neither requires a running postmaster.
Excellent. Let's add some fields to the bug reporting form where people
can paste the output.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
Show quoted text
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
tool for doing 5% of the work and then sitting around waiting for someone
else to do the other 95% so you can sue them.
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the systemand then
creates an email with the information included. Of perhaps a
pg_buginfo like this:pg_config and pg_controldata together cover most if not all of this
info, and neither requires a running postmaster.Excellent. Let's add some fields to the bug reporting form
where people can paste the output.
Probably a good idea. With those, we don't really need specific
questions about locale, right?
And those fields would definitly have to be made optional, I think. But
just adding two optional fields:
Output from pg_config:
Output from pg_controldata:
should do a lot. With that, we could even remove the version field if we
wanted to - but do we? Might be good to keep it in case ppl have a
question that doesn't need/want pg_config/pg_controldata.
//Magnus
Import Notes
Resolved by subject fallback
"Magnus Hagander" <mha@sollentuna.net> writes:
Output from pg_config:
Output from pg_controldata:
should do a lot. With that, we could even remove the version field if we
wanted to - but do we? Might be good to keep it in case ppl have a
question that doesn't need/want pg_config/pg_controldata.
Also, I had forgotten that 8.1 is the first release in which pg_config
without any argument will give you a brain dump of all it knows. Before
that, it's a lot less friendly ...
The pg_controldata output is probably more interesting in most cases
anyway, so put that question first.
regards, tom lane
----- Original Message -----
From: "Andrew Dunstan" <andrew@dunslane.net>
To: "William ZHANG" <uniware@zedware.org>
Cc: <pgsql-hackers@postgresql.org>
Sent: Thursday, March 16, 2006 11:04 PM
Subject: Re: [HACKERS] Bug report form: locale/encoding
William ZHANG wrote:
Has anyone considered something like "reportbug" in Debian which
collects a certain amount of information about the system and then
creates an email with the information included. Of perhaps a pg_buginfo
like this:It sounds good. Should we setup a bug tracker system for pgsql?
Please start by reviewing previous discussions on this point. We really
don't need to have this discussion every few months.
My apologies.
Now I have read the posts here:
http://archives.postgresql.org/pgsql-hackers/2004-02/msg00853.php
http://archives.postgresql.org/pgsql-hackers/2004-02/msg00964.php
Regards,
William ZHANG