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
When a migration job involves tables with Postgres generated columns, pglogical replication goes down.
We see the following errors when doing setup, during the bulk COPY stage (before replication):
[13321]:ERROR: column "XXXXXXXXX" is a generated column
2024-07-15 15:45:05 UTC:DDD.DDD.DDD.DDD(EEEEEE):pglogical@YYYYYYYYYY:
[13321]:DETAIL: Generated columns cannot be used in COPY.
Soon after seeing this, we see pglogical replication status go down.
We need to figure out how to support generated columns with pglogical and pgbelt.
The text was updated successfully, but these errors were encountered:
When a migration job involves tables with Postgres
generated
columns, pglogical replication goes down.We see the following errors when doing
setup
, during the bulk COPY stage (before replication):Soon after seeing this, we see
pglogical
replication status godown
.We need to figure out how to support generated columns with
pglogical
andpgbelt
.The text was updated successfully, but these errors were encountered: