On 18/3/21 14:03, Stepan Yankevych wrote:
>
> 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
That change table should have at lease few additional columns
* Operation (I/D/U)
* txid
* Commit_time_stamp
If you look at logical decoding, that's basically what you have, isn't
it? It won't go into a table, but you can consume it into one if you
want. Look at for example wal2json for exampl
On Thu, Mar 18, 2021 at 2:03 PM Stepan Yankevych
wrote:
> 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, possibl
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
