Commit805a397

committed

Add more detail why repalloc and pfree do not accept NULL pointers

Per discussion, we choose not to change this. This just gives alittle bit more information.Discussion:https://www.postgresql.org/message-id/flat/cf26e970-8e92-59f1-247a-aa265235075b%40enterprisedb.com

1 parent36389a0 commit805a397Copy full SHA for 805a397

File tree

-0

lines changed

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -67,6 +67,12 @@ chunk might later be repalloc'd larger; it can also be pfree'd without`
`67`	`67`	`error. Similarly, repalloc allows realloc'ing to zero size.`
`68`	`68`
`69`	`69`	`* pfree and repalloc do not accept a NULL pointer. This is intentional.`
	`70`	`+(For repalloc, this is necessary: As mentioned above, repalloc does`
	`71`	`+not depend on the current memory context. But then it needs to know`
	`72`	`+which memory context to do the allocation in. So the first allocation`
	`73`	`+has to be done outside of repalloc. For pfree, this behavior is`
	`74`	`+mostly historical and partially because the extra check would impact`
	`75`	`+performance.)`
`70`	`76`
`71`	`77`
`72`	`78`	`The Current Memory Context`

Comments

(0)