-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm very new to this project and inspired by recent security release, I
started to audit postgresql source against common mistakes with sprintf().
I mostly found problems with sprintf() used on statically allocated
buffers or dynamically allocat
Hi,
I checked all the previous string handling errors and most of them were
already fixed by You. However there were a few left and attached patch
should fix the rest of them.
I used StringInfo only in 2 places and both of them are inside debug
ifdefs. Only performance penalty will come from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I checked all the previous string handling errors and most of them were
already fixed by You. However there were a few left and this patch
should fix the rest of them.
I used StringInfo only in 2 places and both of them are inside debug
ifdefs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Conway wrote:
| [ Sorry, never saw the original email ]
Because it is still hanging in moderation queue ;)
| FYI, we prefer patches in context diff format (diff -c). Also, there
| are some code style rules that most of the backend code follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruce Momjian wrote:
| I have reviewed your patch, and it is a thorough job. Unfortunately,
| our code has drifted dramatically since 7.2 in the areas you patched.
| Would you be able to download our CVS or current snapshot and submit a
| patch based
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a resend of my previous email which was stucked at moderation
approval.. and as I don't know if anyone actually does that in your
list, I'm resending this now.
Hi,
I'm very new to this project and inspired by recent security release, I
start
