Skip to content
Snippets Groups Projects
Commit 95e9f4ed authored by Bruce Momjian's avatar Bruce Momjian
Browse files
parent cc3e9dee
No related branches found
No related tags found
No related merge requests found
Developer's Frequently Asked Questions (FAQ) for PostgreSQL Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Sat May 5 10:33:44 EDT 2007 Last updated: Thu May 31 20:28:04 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
...@@ -149,7 +149,7 @@ General Questions ...@@ -149,7 +149,7 @@ General Questions
patches. If you need help checking the SQL standard, see 1.17. patches. If you need help checking the SQL standard, see 1.17.
8. Provide an implementation overview, preferably in code comments. 8. Provide an implementation overview, preferably in code comments.
Following the surrounding code commenting style is usually a good Following the surrounding code commenting style is usually a good
approach. approach (also see this article).
9. If it is a performance patch, please provide confirming test 9. If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post results to show the benefit of your patch. It is OK to post
patches without this information, though the patch will not be patches without this information, though the patch will not be
......
...@@ -13,7 +13,7 @@ ...@@ -13,7 +13,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for <H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1> PostgreSQL</H1>
<P>Last updated: Sat May 5 10:33:44 EDT 2007</P> <P>Last updated: Thu May 31 20:28:04 EDT 2007</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR> "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
...@@ -208,7 +208,8 @@ ...@@ -208,7 +208,8 @@
<li>Provide an implementation overview, preferably in code comments. <li>Provide an implementation overview, preferably in code comments.
Following the surrounding code commenting style is usually a good Following the surrounding code commenting style is usually a good
approach.</li> approach (also see this <a
href="http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips">article</a>).</li>
<li>If it is a performance patch, please provide confirming test <li>If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post patches results to show the benefit of your patch. It is OK to post patches
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment