Re: Logical WAL streaming & START_REPLICATION - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Logical WAL streaming & START_REPLICATION
Date
Msg-id CADK3HHKJ=-07sqjujufVC21KHU1PSXoEBvRfNom5uymaO-179g@mail.gmail.com
Whole thread Raw
In response to Re: Logical WAL streaming & START_REPLICATION  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-jdbc



On 10 March 2018 at 04:44, Craig Ringer <craig@2ndquadrant.com> wrote:
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.



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.


Craig, good, idea.


Thanks!

 

pgsql-jdbc by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical WAL streaming & START_REPLICATION
Next
From: chalda
Date:
Subject: [pgjdbc/pgjdbc] e5aab1: Adjust XAException return codes for bettercompati...