mirror of https://github.com/postgres/postgres
The CHECK_IS_BINARY_UPGRADE macro is not sufficient security protection if we're going to dereference pass-by-reference arguments before it. But in any case we really need to explicitly check PG_ARGISNULL for all the arguments of a non-strict function, not only the ones we expect null values for. Oversight in commitspull/8/head30982be4e5
andf92fc4c95d
. Found by Andreas Seltenreich. (The other usages in pg_upgrade_support.c seem safe.)
parent
c6aeba353a
commit
939d10cd87
Loading…
Reference in new issue