aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonpath_exec.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-09-14 10:44:23 +0900
committerMichael Paquier <michael@paquier.xyz>2020-09-14 10:44:23 +0900
commitac673a1aaff197f3e01f7bac69da0dd700854e13 (patch)
treec623910b03cf1368683838724a5247f123778636 /src/backend/utils/adt/jsonpath_exec.c
parent19f5a37b9fc48a12c77edafb732543875da2f4a3 (diff)
downloadpostgresql-ac673a1aaff197f3e01f7bac69da0dd700854e13.tar.gz
postgresql-ac673a1aaff197f3e01f7bac69da0dd700854e13.zip
Avoid useless allocations for information of dumpable objects in pg_dump/
If there are no objects of a certain type, there is no need to do an allocation for a set of DumpableObject items. The previous coding did an allocation of 1 byte instead as per the fallback of pg_malloc() in the event of an allocation size of zero. This assigns NULL instead for a set of dumpable objects. A similar rule already applied to findObjectByOid(), so this makes the code more defensive as we would just fail with a pointer dereference instead of attempting to use some incorrect data if a non-existing, positive, OID is given by a caller of this function. Author: Daniel Gustafsson Reviewed-by: Julien Rouhaud, Ranier Vilela Discussion: https://postgr.es/m/26C43E58-BDD0-4F1A-97CC-4A07B52E32C5@yesql.se
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions