postgresql/doc/bug.template
Tom Lane ca9112a424 Stamp HEAD as 10devel.
This is a good bit more complicated than the average new-version stamping
commit, because it includes various adjustments in pursuit of changing
from three-part to two-part version numbers.  It's likely some further
work will be needed around that change; but this is enough to get through
the regression tests, at least in Unix builds.

Peter Eisentraut and Tom Lane
2016-08-15 13:49:49 -04:00

54 lines
1.5 KiB
Plaintext

If PostgreSQL failed to compile on your computer or you found a bug,
please fill out this form 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-hackers@postgresql.org instead. Please use the
command "diff -c" to generate the patch.
You may also enter a bug report at http://www.postgresql.org/ instead of
e-mailing this form.
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name :
Your email address :
System Configuration:
---------------------
Architecture (example: Intel Pentium) :
Operating System (example: Linux 2.4.18) :
PostgreSQL version (example: PostgreSQL 10devel): PostgreSQL 10devel
Compiler used (example: gcc 3.3.5) :
Please enter a FULL description of your problem:
------------------------------------------------
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------