distdir = postgrespro-$(VERSION)

echo "<!ENTITY version \"$(VERSION)\">"; \

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

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

<para>

Another method is to fill in the bug report web-form available

at the project's

<ulink url="http://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.

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

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

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

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

email addresses are closed mailing lists. That is, you need to be

subscribed to a list to be allowed to post on it. (You need not be

subscribed to use the bug-report web form, however.)

If you would like to send mail but do not want to receive list traffic,

you can subscribe and set your subscription option to <literal>nomail</>.

For more information send mail to

<email>majordomo@postgresql.org</email>

with the single word <literal>help</> in the body of the message.

</para>

</note>