Patch: Code comments: why some text-handling functions are leakproof - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Patch: Code comments: why some text-handling functions are leakproof
Date
Msg-id CABwTF4Wjp3q=dv6wGgqmFxuE7ZJmas=R_BjJrQHnJwkHzZmd9g@mail.gmail.com
Whole thread Raw
Responses Re: Patch: Code comments: why some text-handling functions are leakproof
List pgsql-hackers
Please see attached a small patch to document why some text-processing functions are marked as leakproof, while some others are not.

This is more or less a verbatim copy of Tom's comment in email thread at [1].

I could not find an appropriate spot to place these comments, so I placed them on bttextcmp() function, The only other place that I could see we can place these comments is in the file src/backend/optimizer/README, because there is some consideration given to leakproof functions in optimizer docs. But these comments seem quite out of place in optimizer docs.


Best regards,
--
Attachment

pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Isn't wait_for_catchup slightly broken?
Next
From: Michael Paquier
Date:
Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set