Home • Explore • Blog • CI
☰



postgresql
5th chunk of `doc/src/sgml/problems.sgml`
adb681626ff6ef4deedf4b8d1903b033c96c586bb207429c000000010000084f
 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="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">article</ulink>
   that outlines some more tips on reporting bugs.
  </para>

  <para>
   Do not spend all your time to figure out which changes in the input make
   the problem go away. This will probably not help solving it. If it turns
   out that the bug cannot be fixed right away, you will still have time to
   find and share your work-around. Also, once again, do not waste your time
   guessing why the bug exists. We will find that out soon enough.
  </para>

  <para>
   When writing a bug report, please avoid confusing terminology.
   The software package in total is called <quote>PostgreSQL</quote>,
   sometimes <quote>Postgres</quote> for short. If you
   are specifically talking about the backend process, mention that, do not
   just say <quote>PostgreSQL crashes</quote>.  A crash of a single
   backend process is quite different from crash of the parent
   <quote>postgres</quote> process; please don't say <quote>the server
   crashed</quote> when you mean a single backend process went down, nor vice versa.
   Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
   are completely separate from the backend.  Please try to be specific
   about whether the problem is on the client or server side.
  </para>
 </sect2>

 <sect2 id="bug-reporting-where-to-report-bugs">
  <title>Where to Report Bugs</title>

  <para>
   In general, send bug reports to the bug report mailing list at
   <email>pgsql-bugs@lists.postgresql.org</email>.
   You are requested to use a descriptive subject for your email
   message, perhaps parts of the error message.
  </para>

  <para>
   Another method is to fill in the bug report web-form available
   at the project's
   <ulink url="https://www.postgresql.org/account/submitbug/">web site</ulink>.
   Entering a bug report this way causes it to be mailed to the
   <email>pgsql-bugs@lists.postgresql.org</email>
Title: Best Practices for Reporting PostgreSQL Bugs
Summary
When reporting bugs in PostgreSQL, avoid using confusing terminology, be specific about the issue, and do not waste time trying to identify workarounds or guessing the cause of the bug; instead, submit bug reports to the pgsql-bugs mailing list or through the project's web site with a descriptive subject and clear details.