Arunprasad Rajkumar
Arunprasad Rajkumar
Attempt copying extension using `pgcopydb copy extensions` and interrupt the copy in the middle. When you resume extension copy again, it would attempt copying already processed extension configuration tables. I...
Solution: Skip generated columns while decoding logical messages. Accessing the SQLite catalog for each DML message might incur performance overhead. To avoid this, the transform process prepares an in-memory cache...
As far as the extension migration is concerned, pgcopydb supports either all or nothing approach via `--skip-extensions` CLI flag. While it might work for most use cases, it does not...
I'm keeping it as draft, I'm still not sure whether we should copy all extension config tables under single txn or open a txn per extension.
Running pgcopydb inside docker causes trouble while using pid to determine who is owning the table for copying. Docker container will be running on their own pid namespace causing it...
PG16 supports logical replication from [standbys](https://www.postgresql.org/docs/current/release-16.html#RELEASE-16-LOGICAL), it would be great if pgcopydb also supports the same. There is a [nice blog post ](https://blog.peerdb.io/real-time-change-data-capture-from-postgres-16-read-replicas)from PeerDB folks on how to leverage standby...
This commit remembers the file write position of a last successful transaction in a undo file. If there's a crash and we need to restart, we use this undo file...
This will drop the existing replication slot and recreates a new one.
This is what I get when I query the pg_stat_replication. ``` pid | 457376 usesysid | 16418 usename | tsdbadmin application_name | pgcopydb client_addr | xxxxxx client_hostname | client_port |...
``` Failed to release a lock with semaphore 2031674: Invalid argument 542165 Failed to acquire a lock with semaphore 2031674: Invalid argument 2023-10-19 01:21:12 542165 SQL pgsql.c:508 Connecting to [source]...