-
Type:
Bug
-
Status: Open
-
Priority:
Low
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Documentation bug:
On the official doc https://www.percona.com/doc/percona-xtradb-cluster/LATEST/limitation.html , PK is not listed as a limitation, where as in Galera documentation is: http://galeracluster.com/documentation-webpages/limitations.html .
I think this should be listed as a limitation even if it can be relaxed when setting `pxc_strict_mode = DISABLED;` :
PXC: root@localhost (test) > insert into t1 values (1);
ERROR 1105 (HY000): Percona-XtraDB-Cluster prohibits use of DML command on a table (test.t1) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER
PXC: root@localhost (test) > SET GLOBAL pxc_strict_mode = DISABLED;
Query OK, 0 rows affected (0.00 sec)
PXC: root@localhost (test) > insert into t1 values (1);
Query OK, 1 row affected (0.00 sec)
Because "LOCK TABLES" is also a limitation listed which can be relaxed with `pxc_strict_mode = DISABLED;`
PXC: root@localhost (test) > LOCK TABLES t1 READ;
ERROR 1105 (HY000): Percona-XtraDB-Cluster prohibits use of LOCK TABLE/FLUSH TABLE <table> WITH READ LOCK with pxc_strict_mode = ENFORCING
PXC: root@localhost (test) > SET GLOBAL pxc_strict_mode = DISABLED;
Query OK, 0 rows affected (0.00 sec)
PXC: root@localhost (test) > LOCK TABLES t1 READ;
Query OK, 0 rows affected (0.00 sec)
Not having PK as a limitation but having "LOCK TABLE" as a limitation is an inconsistency