Generated Columns break `pgbelt`
- Dominant language
- Python
- Stars
- 22
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
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`.
Contributor guide
Research direction
Start with the setup flow and its bulk COPY stage, reproducing the failure with a Postgres table containing a generated column. Trace how pglogical handles the COPY and inspect the reported generated-column error. Done means migrations support such tables and pglogical replication remains up after setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100