Good point about sequence IDs. Another, mroe recent method that's bound to be more foolproof is to track the actual transaction log. Postgres exposes an API fo

Good point about sequence IDs. Another, mroe recent method that's bound to be more foolproof is to track the actual transaction log. Postgres exposes an API for "logical decoding" of said log. The downside is that it's fairly new, Postgres-specific, and I also suspect it puts more burden on the client, which has to interpret the entries and determine if/how they should be indexed. But in theory it gives you a completely data-loss-proof, application-independent way of streaming changes from Postgres.