Re: Logical WAL streaming & START_REPLICATION

On 10 March 2018 at 01:50, Dave Cramer <pg@fastcrypt.com> wrote:

On 9 March 2018 at 01:55, Craig Ringer <craig@2ndquadrant.com> wrote:

On 9 March 2018 at 09:50, Craig Ringer <craig@2ndquadrant.com> wrote:

 

If your system will forget work on crash, it's not flushed, and you shouldn't report it flushed.

I haven't checked to see if PgJDBC actually exposes separate control of the reported flush position though.  If it doesn't, it really must in order to make replication slots work properly.

Yes, we have separate control 

https://github.com/pgjdbc/pgjdbc/blob/1be8a9ebafbfbcff118385a61a350745addcaf3d/pgjdbc/src/main/java/org/postgresql/core/v3/replication/V3PGReplicationStream.java#L97

Great!

I hope that answers your question then Joe.

Dave, if you'd find it useful to add the explanation I wrote to the docs, please feel free to crib as desired.