From df64c24a31e110327135a8590c4500887e4773ae Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Wed, 10 Aug 2022 14:16:31 +0200 Subject: [PATCH] Fix typo in test_oat_hooks README Discussion: https://postgr.es/m/3F066AFE-19F9-4DF5-A498-B09643857A39@yesql.se --- src/test/modules/test_oat_hooks/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/test/modules/test_oat_hooks/README b/src/test/modules/test_oat_hooks/README index a7c400c7475..70c792a4f47 100644 --- a/src/test/modules/test_oat_hooks/README +++ b/src/test/modules/test_oat_hooks/README @@ -28,7 +28,7 @@ The following configuration parameters (GUCs) control this test module's Object Access Type (OAT), Process Utility and Executor Check Permissions hooks. The general pattern is that each hook has a corresponding GUC which controls whether the hook will allow or deny operations for which the hook gets called. -A real-world OAT hook should certainly provide more fine-grained conrol than +A real-world OAT hook should certainly provide more fine-grained control than merely "allow-all" vs. "deny-all", but for testing this is sufficient. Note that even when these hooks allow an action, the core permissions system