pg_flo

Yeah, it would be, since its using logical replication. However, the standard logical replication limitation applies [1] pg_flo can perform common DDLs for you (not something that's in built in logical replication today, hopefully soon) [2] [1] https://www.postgresql.org/docs/current/logical-replication-... [2] https://github.com/shayonj/pg_flo/blob/0e8b6b9ca1caf768b71d3...

Heya! v0.0.4 is now out with `--copy` support, which will stream all the data from the table and the transformation/routing will get applied before the changes land in destination. [1] https://github.com/shayonj/pg_flo?tab=readme-ov-file#streami... [2] https://github.com/shayonj/pg_flo/releases

Yeah, totally fair. Are you ok with a NATS dependency ? Happy to work with you in supporting a new destination like ES. Also looking to make NATS optional for smaller/simpler setups (https://github.com/shayonj/pg_flo/issues/21)

amazing! Will plan a release by Tuesday latest. You can experiment with `--copy-and-stream ` in the meantime [1] [1] https://github.com/shayonj/pg_flo?tab=readme-ov-file#streami...

I think this also might be of interest to you - just one time copies and apply transformations - https://github.com/shayonj/pg_flo/issues/6. I will look into shipping that very soon.

I pushed out the v1. More deets at: https://github.com/shayonj/pg_flo/blob/main/pkg/routing/READ...

Here is a simple example [1] where you can setup a replication for to send data for events tables where tenant_id = `3`. You can setup multiple groups, where each group could be a tenant [2]. Would love to hear more about the use case. I can see the use case being a bit more dynamic, where you don't have to custom define ids per se (?). [1] https://github.com/shayonj/pg_flo/blob/main/internal/multi_t... [2] https://github.com/shayonj/pg_flo/tree/main?tab=readme-ov-fi...