Martin Kleppmann

@shashank025 Good point. AFAIK it's not possible for clients to control when log compaction happens, so if you want to be sure that you see the full set of changes...

@edenhill Thanks for chiming in. I didn't realise that librdkafka may currently reorder messages. As Bottled Water relies on message ordering for correctness, it would be great to have a...

Allowing only one outstanding produce request per topic-partition seems like it might be ok — any produce requests that are issued while one request is in flight would have to...

Hi @ruimarinho, I can see how this would be useful. For updates, people may also want to know the old contents of the row. How do you imagine this would...

> What would be the advantages of running bottledwater in-process compared to those decoders (e.g. wal2json)? @ruimarinho The biggest feature of Bottled Water, in my opinion, is that it coordinates...

A use case for this API is situations where a consumer needs to be sure that it sees all the writes for a particular transaction (rather than just the latest...

Renamed this issue since its meaning has drifted. It's technically already possible for consumers to get access to the stream of events from the logical replication client (the `kafka/` submodule...

Hi @zmaril, thanks for your comments. - Regarding preserving foreign keys and transaction structure: for this purpose, I think you're better off consuming directly from Postgres and not going via...

Yeah, that makes sense. There are two different things we could potentially test: - Consuming the change stream directly from Postgres would give the strongest consistency (the relay could make...

My proposal for a new encoding is as follows: - `timestamp {with,without} time zone` are represented as 64-bit microseconds since the 1970 epoch. `-infinity` and `infinity` are represented as -2^63...