diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index 890545a9b6f9258849250ff9c9209c4deacea88e..cffc1d3939665d32f65a2b0d4100f4959d327146 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -1,7 +1,7 @@ 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) @@ -149,7 +149,7 @@ General Questions patches. If you need help checking the SQL standard, see 1.17. 8. Provide an implementation overview, preferably in code comments. 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 results to show the benefit of your patch. It is OK to post patches without this information, though the patch will not be diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 868a3edc0cf3ef873bafa264379a26b35838b8fd..754baff2f718729d7ba8e5c24ca78ceb98ec0fea 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -13,7 +13,7 @@

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)
@@ -208,7 +208,8 @@

  • Provide an implementation overview, preferably in code comments. Following the surrounding code commenting style is usually a good - approach.
  • + approach (also see this article).
  • If it is a performance patch, please provide confirming test results to show the benefit of your patch. It is OK to post patches