| From: | Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | CDC feature request |
| Date: | 2021-03-18 13:03:17 |
| Message-ID: | VE1PR03MB5312B502C4F7F107D1442C6292699@VE1PR03MB5312.eurprd03.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi All!
Hopefully I’m using correct mail list
If not please show me right direction 😊
I’m quite struggling without native Change Data Capture feature in PostgreSQL.
That would be great to implement it, possibly in not so complicated way.
Can Logical replication be a little be modified or reused to do not replicate data into destination table as is but to insert each change into “change table” (like in oracle 11 CDC)?
That change table should have at lease few additional columns
* Operation (I/D/U)
* txid
* Commit_time_stamp
Thanks!
Stepan Yankevych
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2021-03-18 13:06:33 | Re: A reloption for partitioned tables - parallel_workers |
| Previous Message | John Naylor | 2021-03-18 12:51:46 | Re: popcount |