pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7445869e1b0d369af9125c9db8196a3be3f44463 Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e3897a3a4c559e20ba2c4f311be6ace8006f9005 Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7ad458e06b1bf1408d9d089a843070943d6c7c6a Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4dbe72d61ac6dc1ed4a230db2adec1dc01041f7f Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/df6fea51f01d38a427ed7c5d2e13c501f0beb4f0 Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
pgsql: Fix come incorrect elog() messages in aclchk.c
Fix come incorrect elog() messages in aclchk.c Three error strings used with cache lookup failures were referring to incorrect object types for ACL checks: - Schemas - Types - Foreign Servers There errors should never be triggered, but if they do incorrect information would be reported. Author: Justin Pryzby Discussion: https://postgr.es/m/20221222153041.gn1...@telsasoft.com Backpatch-through: 11 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2fcf685f6daa4f872ca726e25cc504a544916dbb Modified Files -- src/backend/catalog/aclchk.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
