If PostgreSQL failed to compile on your computer or you found a bug that
-is likely to be specific to one platform then please fill out this form
+is likely to be specific to one platform, then please fill out this form
and e-mail it to pgsql-ports@postgresql.org.
-To report any other bug, fill out the form below and e-mail it to
+To report non-porting-related bugs, fill out the form below and e-mail it to
pgsql-bugs@postgresql.org.
+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 pgsql-bugs.
+Security issues can be reported privately to security@postgresql.org.
+
If you not only found the problem but solved it and generated a patch
then e-mail it to pgsql-patches@postgresql.org instead. Please use the
command "diff -c" to generate the patch.
<!--
-$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.19 2004/08/24 00:06:50 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp $
-->
<sect1 id="bug-reporting">
<email>pgsql-bugs@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@postgresql.org</email> or
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.
+ discussion about your bug report on <literal>pgsql-hackers</literal>,
+ if the problem needs more review.
</para>
<para>