Jeremy,
* Jeremy Kerr (jk@ozlabs.org) wrote:
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
>
> ---
> src/backend/utils/adt/varchar.c | 24 +++++++++++++++++++++---
> 1 file changed, 21 insertions(+), 3 deletions(-)
Thanks for the contribution. A couple of comments:
The documentation for submitting a patch to PostgreSQL is here:
http://wiki.postgresql.org/wiki/Submitting_a_Patch
There is also a Developer FAQ available here:
http://wiki.postgresql.org/wiki/Developer_FAQ
The PostgreSQL core folks prefer context diffs (it's not my preference,
but I'm not part of core, nor am I a committer :).
There are a number of things requested to be included with a patch, but
in particular I would point out:
----
Which CVS branch the patch is against (ordinarily this will be HEAD).
Whether it compiles and tests successfully, so we know nothing obvious
is broken.
Whether it contains any platform-specific items and if so, has it been
tested on other platforms.
Describe the effect your patch has on performance, if any. If the patch
is intended to improve performance, it's a good idea to include some
reproducible tests to demonstrate the improvement.
----
You might check out sections 3 & 6 of src/include/c.h. Section 3
defines standard system types, while section 6 defines some widely
useful macros; in particular our custom MemSet and MemSetAligned, which
work on aligned memory structures for improved performance.
Thanks,
Stephen