Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit12d5f27

Browse files
committed
Update problems.sgml
1 parent97ccea7 commit12d5f27

File tree

1 file changed

+15
-5
lines changed

1 file changed

+15
-5
lines changed

‎doc/src/sgml/problems.sgml

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -295,15 +295,24 @@
295295
<title>Where to Report Bugs</title>
296296

297297
<para>
298-
In general, send bug reports to the bug report our support email
299-
address at
298+
In general, send bug reports to our support email address at
300299
<email>bugs@postgrespro.ru</email>.
301300
You are requested to use a descriptive subject for your email
302301
message, perhaps parts of the error message.
303302
</para>
304303

305304
<para>
306-
Do not send bug reports to any of the user mailing lists, such as
305+
Do not send bug reports specific to <productname>Postgres Pro</>
306+
to the <productname>PostgreSQL</> support email address,
307+
as <productname>Postgres Pro</> is not supported by
308+
the <productname>PostgreSQL</> community.
309+
But you can send reports to <email>bugs@postgresql.org</email>
310+
for any bugs related to <productname>PostgreSQL</>.
311+
</para>
312+
313+
<para>
314+
Even if your bug is not specific to <productname>Postgres Pro</>,
315+
do not send bug reports to any of the user mailing lists, such as
307316
<email>pgsql-sql@postgresql.org</email> or
308317
<email>pgsql-general@postgresql.org</email>.
309318
These mailing lists are for answering
@@ -316,9 +325,10 @@
316325
the developers' mailing list <email>pgsql-hackers@postgresql.org</email>.
317326
This list is for discussing the
318327
development of <productname>PostgreSQL</productname>, and it would be nice
319-
if we could keep the bug reports separate. We might choose to take up a
328+
if the community could keep the bug reports separate.
329+
The community might choose to take up a
320330
discussion about your bug report on <literal>pgsql-hackers</literal>,
321-
if the problem needs more review.
331+
if the<productname>PostgreSQL</>-relatedproblem needs more review.
322332
</para>
323333
</sect2>
324334
</sect1>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp