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> mailing list.
  </para>

  <para>
   If your bug report has security implications and you'd prefer that it
   not become immediately visible in public archives, don't send it to
   <literal>pgsql-bugs</literal>.  Security issues can be
   reported privately to <email>security@postgresql.org</email>.
  </para>

  <para>
   Do not send bug reports to any of the user mailing lists, such as
   <email>pgsql-sql@lists.postgresql.org</email> or
   <email>pgsql-general@lists.postgresql.org</email>.
   These mailing lists are for answering
   user questions, and their subscribers normally do not wish to receive
   bug reports. More importantly, they are unlikely to fix them.
  </para>

  <para>
   Also, please do <emphasis>not</emphasis> send reports to
   the developers' mailing list <email>pgsql-hackers@lists.postgresql.org</email>.
   This list is for discussing the
   development of <productname>PostgreSQL</productname>, and it would be nice
   if we could keep the bug reports separate. We might choose to take up a
   discussion about your bug report on <literal>pgsql-hackers</literal>,
   if the problem needs more review.
  </para>

  <para>
   If you have a problem with the documentation, the best place to report it
   is the documentation mailing list <email>pgsql-docs@lists.postgresql.org</email>.
   Please be specific about what part of the documentation you are unhappy
   with.
  </para>

  <para>
   If your bug is a portability problem on a non-supported platform,
   send mail to <email>pgsql-hackers@lists.postgresql.org</email>,
   so we (and you) can work on
   porting <productname>PostgreSQL</productname> to your platform.
  </para>

  <note>
   <para>
    Due to the unfortunate amount of spam going around, all of the above
    lists will be moderated unless you are subscribed. That means there
    will be some delay before the email is delivered. If you wish to subscribe
    to the lists, please visit
    <ulink url="https://lists.postgresql.org/"></ulink> for instructions.
   </para>
  </note>
 </sect2>
</sect1>