You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix for issue #565 only support UPDATE attributes that are not PRIMARY KEY column.
In YugaByte, updating PRIMARY KEY columns needs special attention because they are currently used for two important purposes.
Partitioning the table.
Ordering rows within one table.
The text was updated successfully, but these errors were encountered:
Test case
1- Create a table.
--- CREATE TABLE tab(id int primary key, name text);
2- Insert 100 rows into table.
--- INSERT INTO tab VALUES(x, 'x'); where x = {1, 2, ..., 100 }
3- Update rows
--- UPDATE tab SET id = id + 1000;
4- Turn OFF prefetch by change kPrefetchLimit to 1
--- File pg_doc_op.h: static const int64_t kPrefetchLimit = 1;
--- Also, it's a mistake to use INT32_MAX as default value for number of prefetched rows. We should use "1024" instead.
… partition, fixed test
Summary:
* Updating primary keys (#659) and row-level partitioning (#5179) were developed concurrently. As a result, `yb_pg_foreign_key` pg_regress test had a semantic merge conflict. This test has been fixed, using the vanilla `foreign_key` test as a reference.
* UPDATE on a partitioned table is not allowed to change a partition (#5310 is tracking this). This is handled correctly, but an error message didn't make it clear what went wrong. That message has been improved.
Test Plan: ybd --java-test 'org.yb.pgsql.TestPgForeignKey#testPgRegress'
Reviewers: dmitry, jason
Reviewed By: jason
Subscribers: mikhail, yql
Differential Revision: https://phabricator.dev.yugabyte.com/D9146
Fix for issue #565 only support UPDATE attributes that are not PRIMARY KEY column.
In YugaByte, updating PRIMARY KEY columns needs special attention because they are currently used for two important purposes.
The text was updated successfully, but these errors were encountered: