Re: BUG #5242: ODBC driver v8.4.1 crashed - Mailing list pgsql-bugs

From Stefan Kaltenbrunner
Subject Re: BUG #5242: ODBC driver v8.4.1 crashed
Date
Msg-id 4B27E4B6.7000702@kaltenbrunner.cc
Whole thread Raw
In response to Re: BUG #5242: ODBC driver v8.4.1 crashed  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: BUG #5242: ODBC driver v8.4.1 crashed  (David Fetter <david@fetter.org>)
Re: BUG #5242: ODBC driver v8.4.1 crashed  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
Alvaro Herrera wrote:
> Stefan Kaltenbrunner escribió:
>
>> hmm - not sure that is too clear especially because I don't think
>> ther is only JDBC/ODBC or pgadmin (nor do I think you names match up
>> with how they are really called). what about doing it the other way
>> round like:
>>
>> "This bug report form can be used for reporting bugs and problems
>> with the PostgreSQL database, for problems with database connectors,
>> graphical administration tools or other external projects please
>> report to them directly. Alternatively you can look at the available
>> <a href='/community/lists'>mailing lists</a> and see if there is a
>> more apropriate list available."
>
> I think it's a good idea to mention some specific more problematic names
> like the three listed.

yeah maybe - but afaik the products are not named "psql-odbc" or
"pgsql-jdbc" - those are more or less list names and likely not of much
more use than not listening them at all :).
Plus a lot of the surounding projects (like pgadmin, slony or most
pgfoundry projects) have their own bug/issue reporting/tracking
infrastructure.
I'm all open for better wordings - any other takers? :)


Stefan

pgsql-bugs by date:

Previous
From: postgres bee
Date:
Subject: Inserts taking exponentially longer as table size grows
Next
From: David Fetter
Date:
Subject: Re: BUG #5242: ODBC driver v8.4.1 crashed