Include VARHDRSZ when allocating return value #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the PostgreSQL documentation, the VARHDRSZ header needs to be included in the allocation for the return value. Without this, the allocations are 4 bytes short (which explains the results described in issue #19), writing the data flies off the end of the allocated space (by 4 bytes), and is then overwritten by subsequent allocations.
From the docs:
(Notice the
VARHDRSZ + 40
in both thepalloc()
and theSET_VARSIZE()
calls. While the existing code had+ VARHDRSZ
in theVARSIZE()
call, it was missing frompalloc()
.Fixes #19, and probably #15.
Signed-off-by: Jared Reisinger jaredreisinger@hotmail.com