Cannot create foreign key whose evaluation cannot be enforced to remote nodes

AntDB prompts:

> "cannot create foreign key whose evaluation cannot be enforced to Remote nodes”

How to solve this?

Currently, foreign keys are not allowed to be created on non-sliced keys. The solution is below:

Modify the foreign key field of the child table to be a sliced key and then create a foreign key.
If the data volume of the parent table is small, you can modify the parent table to be a duplicate table.

Reproduction of SQL:

antdb=# create table t_parent (id int primary key,name varchar(30));
create table t_child (id int,name varchar(30)) distribute by hash(name);

CREATE TABLE
antdb=# create table t_child (id int,name varchar(30)) distribute by hash(name);
CREATE TABLE
antdb=# 
antdb=# alter table t_child
postgres-#     add constraint fkey_t_child
postgres-#     foreign key (id) 
postgres-#     references t_parent (id);
ERROR:  Cannot create foreign key whose evaluation cannot be enforced to remote nodes
antdb=#
antdb=# alter table t_child distribute by hash (id);
ALTER TABLE
antdb=# alter table t_child                         
    add constraint fkey_t_child
    foreign key (id) 
    references t_parent (id);
ALTER TABLE

antdb=# drop table t_child;
DROP TABLE
antdb=# create table t_child (id int,name varchar(30)) distribute by hash(name);
CREATE TABLE
antdb=# alter table t_parent distribute by replication;
ALTER TABLE
antdb=# alter table t_child                            
postgres-#     add constraint fkey_t_child
postgres-#     foreign key (id) 
postgres-#     references t_parent (id);
ALTER TABLE
antdb=# 

fe_sendauth: no password supplied

Possible error message:

WARNING: on coordinator execute "set FORCE_PARALLEL_MODE = off; SELECT adb_PAUSE_CLUSTER();" fail ERROR: error message from poolmgr:reconnect three thimes , fe_sendauth: no password supplied

Solution:
Check the hba information of the coords in the cluster and whether it exists or not: the authentication method for host IP with md5 in the cluster.

Execute :show hba nodename in adbmgr to see the hba information of the node.
FATAL: invalid value for parameter “TimeZone”: “Asia/Shanghai”

Possible error message:

FATAL: invalid value for parameter "TimeZone": "Asia/Shanghai"
FATAL: invalid value for parameter "TimeZone": "asia/shanghai"
FATAL: invalid value for parameter "TimeZone": "utc"

Solution:

Check the JAVA_OPTS of JDBC that whether the user.timezone parameter is configured, if the parameter is configured, you need to strictly match the case of the time zone names supported by default within the database.

Time zones supported in the database use the following sql query. Pay attention to the case of the time zone name.

select * from adb_catalog.adb_timezone_names;

If the parameter is not configured in JDBC, check it as described in step 2.

Check the share in the AntDB binaries directory, and make sure the timezone under timezone is complete. If it is missing or incomplete, you need to deploy the required files from a complete node again.

ll $ADBHOME/share/postgresql/timezone
total 232
drwxr-xr-x 2 antdb antdb 4096 Apr 16 15:59 Africa
drwxr-xr-x 6 antdb antdb 4096 Apr 16 15:59 America
drwxr-xr-x 2 antdb antdb 4096 Apr 16 15:59 Antarctica
drwxr-xr-x 2 antdb antdb   25 Apr 16 15:59 Arctic
drwxr-xr-x 2 antdb antdb 4096 Apr 16 15:59 Asia
......
drwxr-xr-x 2 antdb antdb 4096 Apr 16 15:59 US
-rwxr-xr-x 1 antdb antdb  114 Apr 16 15:48 UTC
-rwxr-xr-x 1 antdb antdb 1905 Apr 16 15:48 WET
-rwxr-xr-x 1 antdb antdb 1535 Apr 16 15:48 W-SU
-rwxr-xr-x 1 antdb antdb  114 Apr 16 15:48 Zulu