From afd1d95f5bf0cb48af77e5897eb4c356b5371c7b Mon Sep 17 00:00:00 2001
From: Stephen Frost <sfrost@snowman.net>
Date: Wed, 24 Sep 2014 17:45:11 -0400
Subject: [PATCH] Copy-editing of row security
Address a few typos in the row security update, pointed out
off-list by Adam Brightwell. Also include 'ALL' in the list
of commands supported, for completeness.
---
doc/src/sgml/ddl.sgml | 10 +++++-----
src/backend/commands/policy.c | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index e5ee5910513..98e897aeb6c 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1535,7 +1535,7 @@ REVOKE ALL ON accounts FROM PUBLIC;
be added through data modification commands. By default, tables do
not have any policies and all rows are visible and able to be added,
subject to the regular <xref linkend="ddl-priv"> system. This is
- also known to as Row Level Security.
+ also known as Row Level Security.
</para>
<para>
@@ -1550,10 +1550,10 @@ REVOKE ALL ON accounts FROM PUBLIC;
<para>
Row security policies can be specific to commands, or to roles, or to
- both. The commands available are <literal>SELECT</>, <literal>INSERT</>,
- <literal>UPDATE</>, and <literal>DELETE</>. Multiple roles can be
- assigned to a given policy and normal role membership and inheiritance
- rules apply.
+ both. The commands available are <literal>ALL</literal>,
+ <literal>SELECT</>, <literal>INSERT</>, <literal>UPDATE</>, and
+ <literal>DELETE</>. Multiple roles can be assigned to a given policy
+ and normal role membership and inheiritance rules apply.
</para>
<para>
diff --git a/src/backend/commands/policy.c b/src/backend/commands/policy.c
index 6bff9500c6b..33bf031346f 100644
--- a/src/backend/commands/policy.c
+++ b/src/backend/commands/policy.c
@@ -108,7 +108,7 @@ parse_row_security_command(const char *cmd_name)
char cmd;
if (!cmd_name)
- elog(ERROR, "unregonized command");
+ elog(ERROR, "unrecognized command");
if (strcmp(cmd_name, "all") == 0)
cmd = 0;
--
GitLab