You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hawq.apache.org by yo...@apache.org on 2016/09/27 21:01:48 UTC
[3/8] incubator-hawq-docs git commit: even more updates - clean up
update, delete, vacuum references
even more updates - clean up update, delete, vacuum references
Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/b6dd1372
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/b6dd1372
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/b6dd1372
Branch: refs/heads/develop
Commit: b6dd13722077d4c2c9acada68c5eff07cc56359e
Parents: 94eac9f
Author: Lisa Owen <lo...@pivotal.io>
Authored: Fri Sep 23 10:27:29 2016 -0700
Committer: Lisa Owen <lo...@pivotal.io>
Committed: Fri Sep 23 10:27:29 2016 -0700
----------------------------------------------------------------------
datamgmt/ConcurrencyControl.html.md.erb | 7 -------
datamgmt/Transactions.html.md.erb | 2 --
reference/sql/GRANT.html.md.erb | 2 +-
3 files changed, 1 insertion(+), 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/b6dd1372/datamgmt/ConcurrencyControl.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/ConcurrencyControl.html.md.erb b/datamgmt/ConcurrencyControl.html.md.erb
index 0291ddb..2ced135 100644
--- a/datamgmt/ConcurrencyControl.html.md.erb
+++ b/datamgmt/ConcurrencyControl.html.md.erb
@@ -17,15 +17,8 @@ HAWQ provides multiple lock modes to control concurrent access to data in tables
| Lock Mode | Associated SQL Commands | Conflicts With |
|------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
| ACCESS SHARE | `SELECT` | ACCESS EXCLUSIVE |
-| ROW SHARE | `SELECT FOR UPDATE`, `SELECT FOR SHARE` | EXCLUSIVE, ACCESS EXCLUSIVE |
| ROW EXCLUSIVE | `INSERT`, `COPY` | SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
| SHARE UPDATE EXCLUSIVE | `VACUUM` (without `FULL`), `ANALYZE` | SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
| SHARE | `CREATE INDEX` | ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
| SHARE ROW EXCLUSIVE | � | ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
-| EXCLUSIVE | `DELETE`, `UPDATE` See [Note](#topic_f5l_qnh_kr__lock_note) | ROW SHARE, ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
| ACCESS EXCLUSIVE | `ALTER TABLE`, `DROP TABLE`, `TRUNCATE`, `REINDEX`, `CLUSTER`, `VACUUM FULL` | ACCESS SHARE, ROW SHARE, ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, ACCESS EXCLUSIVE |
-
-
-**Note:** In HAWQ, `UPDATE` and `DELETE` acquire the more restrictive lock EXCLUSIVE rather than ROW EXCLUSIVE.
-
-
http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/b6dd1372/datamgmt/Transactions.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/Transactions.html.md.erb b/datamgmt/Transactions.html.md.erb
index a057121..dfc9a5e 100644
--- a/datamgmt/Transactions.html.md.erb
+++ b/datamgmt/Transactions.html.md.erb
@@ -49,8 +49,6 @@ A `SELECT` query:
Successive `SELECT` commands within a single transaction always see the same data.
- `SELECT FOR UPDATE` and `SELECT FOR SHARE` commands find only rows committed before the command started. If a concurrent transaction has already locked a target row when the row is found, the serializable or repeatable read transaction waits for the concurrent transaction to update the row, delete the row, or roll back.
-
The default transaction isolation level in HAWQ is *read committed*. To change the isolation level for a transaction, declare the isolation level when you `BEGIN` the transaction or use the `SET TRANSACTION` command after the transaction starts.
http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/b6dd1372/reference/sql/GRANT.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/sql/GRANT.html.md.erb b/reference/sql/GRANT.html.md.erb
index 4baed38..1673df5 100644
--- a/reference/sql/GRANT.html.md.erb
+++ b/reference/sql/GRANT.html.md.erb
@@ -167,7 +167,7 @@ GRANT admins TO joe;
The `PRIVILEGES` key word in is required in the SQL standard, but optional in HAWQ. The SQL standard does not support setting the privileges on more than one object per command.
-HAWQ allows an object owner to revoke his own ordinary privileges: for example, a table owner can make the table read-only to himself by revoking his own `INSERT`, `UPDATE`, and `DELETE` privileges. This is not possible according to the SQL standard. HAWQ treats the owner's privileges as having been granted by the owner to himself; therefore he can revoke them too. In the SQL standard, the owner's privileges are granted by an assumed *system* entity.
+HAWQ allows an object owner to revoke his own ordinary privileges: for example, a table owner can make the table read-only to himself by revoking his own `INSERT` privileges. This is not possible according to the SQL standard. HAWQ treats the owner's privileges as having been granted by the owner to himself; therefore he can revoke them too. In the SQL standard, the owner's privileges are granted by an assumed *system* entity.
The SQL standard allows setting privileges for individual columns within a table.