|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.21 2005/03/25 00:51:04 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <sect1 id="bug-reporting"> |
@@ -265,7 +265,9 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp |
265 | 265 | Do not be afraid if your bug report becomes rather lengthy. That is a fact of life. |
266 | 266 | It is better to report everything the first time than us having to squeeze the |
267 | 267 | facts out of you. On the other hand, if your input files are huge, it is |
268 | | - fair to ask first whether somebody is interested in looking into it. |
| 268 | + fair to ask first whether somebody is interested in looking into it. Here is |
| 269 | + an <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> |
| 270 | + article</ulink> that outlines some more tips on reporting bugs. |
269 | 271 | </para> |
270 | 272 |
|
271 | 273 | <para> |
|