From 0534fb5622430c06b569708e1464f6ad6889aa12 Mon Sep 17 00:00:00 2001 From: Brian Faherty Date: Wed, 27 Jun 2018 15:47:26 -0400 Subject: [PATCH] Fix readme language to be more consistent References to `set_user(text)` and `set_user_u(text)` have been changed from `set_user('rolename')` and `set_user_u('rolename') to `set_user(text)` and `set_user_u(text)`, in contexts where the functions are being referenced and not called. This makes the README easier to follow. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 56f1d7d..9313ad7 100644 --- a/README.md +++ b/README.md @@ -44,8 +44,8 @@ This PostgreSQL extension allows switching users and optional privilege escalation with enhanced logging and control. It provides an additional layer of logging and control when unprivileged users must escalate themselves to superuser or object owner roles in order to perform needed maintenance tasks. -Specifically, when an allowed user executes `set_user('rolename')` or -`set_user_u('rolename')`, several actions occur: +Specifically, when an allowed user executes `set_user(text)` or +`set_user_u(text)`, several actions occur: * The current effective user becomes `rolename`. * The role transition is logged, with a specific notation if `rolename` is a @@ -236,7 +236,7 @@ For the blocking of `ALTER SYSTEM` and `COPY PROGRAM` to work properly, you must include `set_user` in shared_preload_libraries in postgresql.conf and restart PostgreSQL. -Neither `set_user('rolename')` nor `set_user_u('rolename')` may be executed from +Neither `set_user(text)` nor `set_user_u(text)` may be executed from within an explicit transaction block. ## Caveats