21–29 of 29 posts
Do you do anything special with toast not changed values, this always seemed problematic to me with doing cdc as either you have to maintain the latest value in your own state or hit the read connection to pull the value
I'm exploring an alternative way to run logic asynchronously after db operations without the overhead, and I think using cdc to export jobs into an external queue is the way to go here. Essentially a lightweight alternative to Debezium with a better developer experience that is easier to manage. This crate could serve as the core of such a service.
My specific use-case would be: Single Postgres in my cluster, replicated via something based on pg_replicate running as a side-car and writing to my NAS running Minio.
I would love to see this become the [Litestream]( https://litestream.io/ ) equivalent to SQLite: a very cheap option for simple deployments (ones with a single database) to get continuous backups in a cheap storage from which one can restore when needed. My specific use-case would be: Single Postgres in my cluster, replicated via something based on pg_replicate running as a side-car and writing to my NAS running Mini…
> equivalent to SQLite: a very cheap option for simple deployments
FWIW, we will launch something tomorrow which will cover this part of your use-case. You will be able to find it on our blog in the morning (PT)
Wow I think i build one of the first pg-rust-cdc replication module for postgresql and now it seems mainstream. It was a part of my https://github.com/posix4e/rpgffi project, which is garbage code I'm now embarrassed about. Rust programming has come a long way and we didn't have the best practices. Now it seems actual grownup engineering teams are living the dream. We truly live in the best of all universes.
These days, for writing extensions/FFI pgrx[0] is the best crate. [0] https://github.com/pgcentralfoundation/pgrx