pg_restore fails for tables with TRUNCATE TABLE statements during Greenplum migration

Aperta
  • Qualcosa non va?
#2,214 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, postgresql
Ambito
databases

Direzione di ricerca

Start by asking the reporter for the dump snippet, restore command, and complete error logs; these are not included in the issue. Then trace how pg_restore handles the failing TRUNCATE statements and compare the generated syntax with Cloudberry’s restore behavior. Done means reproducing the failure and confirming that the affected tables restore successfully; the issue does not identify a source file or test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hi Apache Cloudberry Team,

We are migrating a database from Greenplum Database 6.21.0 to Apache Cloudberry 2.1.0-incubating using the pg_dump and pg_restore utilities.

During the restore process, we are encountering errors for certain tables where the dump contains only TRUNCATE TABLE statements.

The issue occurs when executing the generated dump file against the target Cloudberry database. Tables associated with TRUNCATE TABLE statements are failing during the restore process.

Environment:

Source Database: Greenplum Database 6.21.0

Target Database: Apache Cloudberry 2.1.0-incubating

Source Database Size: Approximately 2 TB

Operating System: Oracle Linux 9.8

Migration Method: pg_dump and pg_restore

Migration Steps:

Generate a database dump from the Greenplum 6.21.0 source database using pg_dump.

Restore the dump into the Apache Cloudberry 2.1.0-incubating target database using pg_restore.

Observe errors for tables containing TRUNCATE TABLE statements in the dump.

Expected Behavior:

The dump generated from Greenplum should restore successfully in Apache Cloudberry, including tables with TRUNCATE TABLE statements.

Actual Behavior:

The restore process encounters errors for tables where the dump contains TRUNCATE TABLE statements, preventing successful restoration of the affected tables.

Questions:

Is there any known compatibility issue with TRUNCATE TABLE statements generated by pg_dump from Greenplum 6.21.0?

Are there any differences in TRUNCATE TABLE syntax or behavior between Greenplum 6.21.0 and Apache Cloudberry 2.1.0-incubating?

Is there any recommended workaround to successfully restore these tables?

Is this issue already addressed in a later Cloudberry release?

We can provide the relevant dump snippets, restore commands, and complete error logs for further investigation.

Thank you.

Lingua principale
C
Stelle
1.4k
Fork
265
Merge medio
3g 18h
PR unite (30g)
70

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/cloudberry

Tutte le issue di apache/cloudberry

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.