|
|
|
|
@ -1,5 +1,5 @@ |
|
|
|
|
<!-- |
|
|
|
|
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.21 2005/03/25 00:51:04 momjian Exp $ |
|
|
|
|
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.22 2005/03/25 01:01:14 momjian Exp $ |
|
|
|
|
--> |
|
|
|
|
|
|
|
|
|
<sect1 id="bug-reporting"> |
|
|
|
|
@ -266,8 +266,9 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.21 2005/03/25 00:51:04 momjian |
|
|
|
|
It is better to report everything the first time than us having to squeeze the |
|
|
|
|
facts out of you. On the other hand, if your input files are huge, it is |
|
|
|
|
fair to ask first whether somebody is interested in looking into it. Here is |
|
|
|
|
an <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> |
|
|
|
|
article</ulink> that outlines some more tips on reporting bugs. |
|
|
|
|
an article, <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> |
|
|
|
|
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html</ulink>, that outlines |
|
|
|
|
some more tips on reporting bugs. |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
|