leaocx commented on issue #1861:
URL: https://github.com/apache/cloudberry/issues/1861#issuecomment-5056215038
Hi @520yanaji, thanks for reporting this.
We tried to reproduce the issue using your exact command pattern:
```
cbcopy --source-host 127.0.0.1 --source-port 5432 --source-user gpadmin \
--dest-host 127.0.0.1 --dest-port 5432 --dest-user gpadmin \
--dbname test_src --dest-dbname test_dest \
--append --with-global-metadata
```
**Test environment:** Apache Cloudberry 2.4.0, single cluster (source and
destination on the same instance).
**Test setup:** We created a source database with multiple empty tables
covering various scenarios:
- Plain empty tables
- Empty tables with PRIMARY KEY, indexes, and NOT NULL constraints
- Empty partitioned tables (RANGE partitioning with child partitions)
- Empty tables with various data types (serial, numeric, jsonb, arrays,
timestamps, defaults)
- Empty child tables with FOREIGN KEY constraints
- Tables with data (as a control group)
**Result:** With `--dbname --append --with-global-metadata`, **all empty
table structures (DDL) were successfully migrated** to the destination
database, including:
- Table definitions with all column types and defaults
- PRIMARY KEY and indexes
- Partition definitions and child tables
- FOREIGN KEY constraints
- Sequences (serial columns)
Only the data copy phase was skipped for empty tables (which is expected —
no data to copy). The table structures were all created correctly.
We were **unable to reproduce the issue** you described. Could you please
provide the following so we can investigate further?
1. The full `cbcopy` output log (ideally with `--verbose` flag)
2. The exact table definitions in your source database that failed to migrate
3. Whether the destination database (`dm_test`) already had any existing
objects before running cbcopy
This will help us determine whether the issue is related to a specific table
type, a DDL execution error, or something else in your environment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
