mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-02-05 19:09:58 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add URL of how to report bugs:

Browse Source 
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
This commit is contained in:
Bruce Momjian 2005-03-25 00:51:04 +00:00
parent e6befdc9d1
commit 07ebb9fba9
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/problems.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.21 2005/03/25 00:51:04 momjian Exp $
--> -->
<sect1 id="bug-reporting"> <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
Do not be afraid if your bug report becomes rather lengthy. That is a fact of life. Do not be afraid if your bug report becomes rather lengthy. That is a fact of life.
It is better to report everything the first time than us having to squeeze the 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 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. 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.
</para> </para>
<para> <para>