Downgrade errors in object_ownercheck() to internal The "does not exist" errors in object_ownership() were written as ereport(), suggesting that they are user-facing. But no code path except one can reach this function without first checking that the object exists. If this were actually a user-facing error message, then there would be some problems: get_object_class_descr() is meant to be for internal errors only and does not support translation.
The one case that can reach this without first checking the object existence is from be_lo_unlink(). (This makes some sense since large objects are referred to by their OID directly.) In this one case, we can add a line of code to check the object existence explicitly, consistent with other LO code. For the rest, downgrade the error messages to elog()s. The new message wordings are the same as in DropObjectById(). Reviewed-by: Alvaro Herrera <alvhe...@alvh.no-ip.org> Discussion: https://www.postgresql.org/message-id/flat/da2f8942-be6d-48d0-ac1c-a053370a6...@eisentraut.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/de9037d0d085f25d3c220a45bfbb7abc5794a0c8 Modified Files -------------- src/backend/catalog/aclchk.c | 10 ++++------ src/backend/libpq/be-fsstubs.c | 5 +++++ 2 files changed, 9 insertions(+), 6 deletions(-)
