From 6bde5f9945348cc44f0e810bac83063a30a05310 Mon Sep 17 00:00:00 2001
From: Roman Simakov <roman.simakov@gmail.com>
Date: Wed, 26 Oct 2016 10:31:39 +0300
Subject: [PATCH] Adjust sql security doc

---
 doc/sql.extensions/README.sql_security.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/sql.extensions/README.sql_security.txt b/doc/sql.extensions/README.sql_security.txt
index e69ca55770..b0f767196b 100644
--- a/doc/sql.extensions/README.sql_security.txt
+++ b/doc/sql.extensions/README.sql_security.txt
@@ -15,10 +15,13 @@ CREATE [OR ALTER] PROCEDURE <PROCEDURENAME> ... [SQL SECURITY {DEFINER | INVOKER
 CREATE [OR ALTER] TRIGGER <TRIGGERNAME> ... [SQL SECURITY {DEFINER | INVOKER} | DROP SQL SECURITY] [AS ...]
 CREATE [OR ALTER] PACKAGE <PACKAGENAME> [SQL SECURITY {DEFINER | INVOKER}] AS ...
 
+ALTER DATABASE SET DEFAULT SQL SECURITY {DEFINER | INVOKER}
+
 Description:
 
 Makes it possible to execute some objects with permissions of either definer or invoker.
-By default INVOKER is used to keep backward compatibility.
+By default INVOKER is used to keep backward compatibility. You can change this behavior and be more compatible
+with SQL STANDARD by using ALTER DATABASE SET DEFAULT SQL SECURITY statement.
 
 If INVOKER is specified a current set of privileges of the current user will be used.
 If DEFINER - a set of privileges of object owner will be used to check an access to database objects used by this object.