mirror of
https://github.com/postgres/postgres.git
synced 2025-07-05 07:21:24 +03:00
Fix some bogus direct uses of realloc().
pg_dump/parallel.c was using realloc() directly with no error check. While the odds of an actual failure here seem pretty low, Coverity complains about it, so fix by using pg_realloc() instead. While looking for other instances, I noticed a couple of places in psql that hadn't gotten the memo about the availability of pg_realloc. These aren't bugs, since they did have error checks, but verbosely inconsistent code is not a good thing. Back-patch as far as 9.3. 9.2 did not have pg_dump/parallel.c, nor did it have pg_realloc available in all frontend code.
This commit is contained in:
@ -1133,12 +1133,7 @@ exec_command(const char *cmd,
|
||||
while ((opt = psql_scan_slash_option(scan_state,
|
||||
OT_NORMAL, NULL, false)))
|
||||
{
|
||||
newval = realloc(newval, strlen(newval) + strlen(opt) + 1);
|
||||
if (!newval)
|
||||
{
|
||||
psql_error("out of memory\n");
|
||||
exit(EXIT_FAILURE);
|
||||
}
|
||||
newval = pg_realloc(newval, strlen(newval) + strlen(opt) + 1);
|
||||
strcat(newval, opt);
|
||||
free(opt);
|
||||
}
|
||||
|
Reference in New Issue
Block a user