<para>

If you have installation problems on a platform that is known

to be supported according to recent build farm results, please report

it to <email>pgsql-bugs@postgresql.org</email>. If you are interested

it to <email>pgsql-bugs@lists.postgresql.org</email>. If you are interested

in porting <productname>PostgreSQL</> to a new platform,

<email>pgsql-hackers@postgresql.org</email> is the appropriate place

<email>pgsql-hackers@lists.postgresql.org</email> is the appropriate place

to discuss that.

</para>

</sect1>

<para>

In general, send bug reports to the bug report mailing list at

<email>pgsql-bugs@postgresql.org</email>.

<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>

at the project's

<ulink url="https://www.postgresql.org/">web site</ulink>.

Entering a bug report this way causes it to be mailed to the

<email>pgsql-bugs@postgresql.org</email> mailing list.

<email>pgsql-bugs@lists.postgresql.org</email> mailing list.

</para>

<para>

<para>

Do not send bug reports to any of the user mailing lists, such as

<email>pgsql-sql@postgresql.org</email> or

<email>pgsql-general@postgresql.org</email>.

<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@postgresql.org</email>.

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

<para>

If you have a problem with the documentation, the best place to report it

is the documentation mailing list <email>pgsql-docs@postgresql.org</email>.

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@postgresql.org</email>,

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>

<xsl:paramname="make.valid.html"select="1"></xsl:param>

<xsl:paramname="generate.id.attributes"select="1"></xsl:param>

<xsl:paramname="generate.legalnotice.link"select="1"></xsl:param>

<xsl:paramname="link.mailto.url">pgsql-docs@postgresql.org</xsl:param>

<xsl:paramname="link.mailto.url">pgsql-docs@lists.postgresql.org</xsl:param>

<xsl:paramname="chunker.output.indent"select="'yes'"/>

<xsl:paramname="chunk.quietly"select="1"></xsl:param>

<xsl:paramname="make.valid.html"select="1"></xsl:param>

<xsl:paramname="generate.id.attributes"select="1"></xsl:param>

<xsl:paramname="link.mailto.url">pgsql-docs@postgresql.org</xsl:param>

<xsl:paramname="link.mailto.url">pgsql-docs@lists.postgresql.org</xsl:param>

<xsl:paramname="toc.max.depth">2</xsl:param>

you are encouraged to try converting your applications. If you

find that some of the functionality of this module is not

available in an adequate form with the newer API, please explain

your issue to <email>pgsql-hackers@postgresql.org</email> so that the deficiency

your issue to <email>pgsql-hackers@lists.postgresql.org</email> so that the deficiency

can be addressed.

</para>

</sect2>