-
### Describe:
 SELECT /*+ keep_result */ DISTINCT \ FROM \ GROUP BY \ LIMIT \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL with CP…
-
### Describe:
 SELECT /*+ keep_table_function_result */ \ FROM \ LIMIT \ OFFSET \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL wit…
-
### Describe:
 SELECT /*+ keep_result */ \ FROM \ LIMIT \ OFFSET \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL with CPU-only Conf…
-
### Describe:
 SELECT DISTINCT \ FROM \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL with CPU-only Config:***
```sql
CREATE …
-
### Describe:
 SELECT /*+ keep_table_function_result */ \ FROM \ GROUP BY \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL with CPU-…
-
### Describe:
 SELECT \ FROM \ brings different results, when using CPU-only configurations and GPU-used configurations.
#### ***SQL with CPU-only Config:***
```sql
CREATE TABLE t0(…
-
### Describe:
HeavyDB will crash when insert values after create table with too small or large pagesize, after SET EXECUTOR_DEVICE='GPU'.
It is worth mentioning that no error report when create…
-
### Describe:
Using SELECT \* FROM \ WHERE ((\ + \) < \) OR (\ = \) brings different results , when set EXECUTOR\_DEVICE 'CPU' and 'GPU'.
#### ***SQL:***
```sql
CREATE TABLE t0(c0 INT);
INS…
-
### Describe:
Using SELECT DISTINCT \ FROM \ ORDER BY 1 DESC LIMIT 10 brings different results , when set EXECUTOR\_DEVICE 'CPU' and 'GPU'.
#### ***SQL:***
```sql
CREATE TABLE t0(c0 INT, c1 …
-
I have two servers, each has a heavydb docker container: `heavyai/heavyai-ee-cuda`.
I am following the documentation to configure a distributed setup.
Server Configuration:
Server 10.0.0.5: Conf…