-
+
PostgreSQL Coding Conventions
while>, switch>, etc go on their own lines.
+ Limit line lengths so that the code is readable in an 80-column window.
+ (This doesn't mean that you must never go past 80 columns. For instance,
+ breaking a long error message string in arbitrary places just to keep the
+ code within 80 columns is probably not a net gain in readability.)
+
+
Do not use C++ style comments (//> comments). Strict ANSI C
compilers do not accept them. For the same reason, do not use C++
rules, it's a good idea to do so. Your code will get run through
pgindent> before the next release, so there's no point in
making it look nice under some other set of formatting conventions.
+ A good rule of thumb for patches is make the new code look like
+ the existing code around it>.