|
295 | 295 | <title>Where to Report Bugs</title> |
296 | 296 |
|
297 | 297 | <para> |
298 | | - In general, send bug reports to the bug report mailing list at |
299 | | - <email>pgsql-bugs@postgresql.org</email>. |
| 298 | + In general, send bug reports to the bug report our support email |
| 299 | + address at |
| 300 | + <email>bugs@postgrespro.ru</email>. |
300 | 301 | You are requested to use a descriptive subject for your email |
301 | 302 | message, perhaps parts of the error message. |
302 | 303 | </para> |
303 | 304 |
|
304 | | - <para> |
305 | | - Another method is to fill in the bug report web-form available |
306 | | - at the project's |
307 | | - <ulink url="http://www.postgresql.org/">web site</ulink>. |
308 | | - Entering a bug report this way causes it to be mailed to the |
309 | | - <email>pgsql-bugs@postgresql.org</email> mailing list. |
310 | | - </para> |
311 | | - |
312 | | - <para> |
313 | | - If your bug report has security implications and you'd prefer that it |
314 | | - not become immediately visible in public archives, don't send it to |
315 | | - <literal>pgsql-bugs</literal>. Security issues can be |
316 | | - reported privately to <email>security@postgresql.org</email>. |
317 | | - </para> |
318 | | - |
319 | 305 | <para> |
320 | 306 | Do not send bug reports to any of the user mailing lists, such as |
321 | 307 | <email>pgsql-sql@postgresql.org</email> or |
|
334 | 320 | discussion about your bug report on <literal>pgsql-hackers</literal>, |
335 | 321 | if the problem needs more review. |
336 | 322 | </para> |
337 | | - |
338 | | - <para> |
339 | | - If you have a problem with the documentation, the best place to report it |
340 | | - is the documentation mailing list <email>pgsql-docs@postgresql.org</email>. |
341 | | - Please be specific about what part of the documentation you are unhappy |
342 | | - with. |
343 | | - </para> |
344 | | - |
345 | | - <para> |
346 | | - If your bug is a portability problem on a non-supported platform, |
347 | | - send mail to <email>pgsql-hackers@postgresql.org</email>, |
348 | | - so we (and you) can work on |
349 | | - porting <productname>PostgreSQL</productname> to your platform. |
350 | | - </para> |
351 | | - |
352 | | - <note> |
353 | | - <para> |
354 | | - Due to the unfortunate amount of spam going around, all of the above |
355 | | - email addresses are closed mailing lists. That is, you need to be |
356 | | - subscribed to a list to be allowed to post on it. (You need not be |
357 | | - subscribed to use the bug-report web form, however.) |
358 | | - If you would like to send mail but do not want to receive list traffic, |
359 | | - you can subscribe and set your subscription option to <literal>nomail</>. |
360 | | - For more information send mail to |
361 | | - <email>majordomo@postgresql.org</email> |
362 | | - with the single word <literal>help</> in the body of the message. |
363 | | - </para> |
364 | | - </note> |
365 | 323 | </sect2> |
366 | 324 | </sect1> |