PostgreSQL错误报告准则:Bug Reporting Guidelines
最新学讯:近期OCP认证正在报名中,因考试人员较多请尽快报名获取最近考试时间,报名费用请联系在线老师,甲骨文官方认证,报名从速!
我要咨询Bug Reporting Guidelines
When you find a bug in PostgreSQL we want to hear about it. Your bug reports play an important part in making PostgreSQL more reliable because even the utmost care cannot guarantee that every part of PostgreSQL will work on every platform under every circumstance.
The following suggestions are intended to assist you in forming bug reports that can be handled in an effective fashion. No one is required to follow them but doing so tends to be to everyone's advantage.
We cannot promise to fix every bug right away. If the bug is obvious, critical, or affects a lot of users,chances are good that someone will look into it. It could also happen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is simply too hard and there are more important things on the agenda. If you need help immediately, consider obtaining a commercial
support contract.
错误报告准则
当您在PostgreSQL中发现错误时,我们想听听它。您的错误报告起着重要作用使PostgreSQL更可靠,因为即使是最大的注意也不能保证PostgreSQL在每个部分、在任何情况下、在每个平台上都正常运行。
以下建议旨在帮助您更有效的方式提交错误报告。没有人需要必须按这些建议,但是这样做往往对每个人都是有利的。
我们不能保证立即修复每个错误。如果该错误是明显的、严重的、或影响了很多用户,调查它的机会很大。我们还可能会告诉您更新至较新的版本,以查看错误是否还会发生。或者我们在决定重写的下一个大版本才会修复。也许这太难了,并且有议程上更重要的事情。如果您立即需要帮助,请考虑购买商业支持合同。