Re: Logical WAL streaming & START_REPLICATION
| От | Craig Ringer |
|---|---|
| Тема | Re: Logical WAL streaming & START_REPLICATION |
| Дата | |
| Msg-id | CAMsr+YEM_QhxkhAS2g8LdPGjFDC9wLwk5BF-5t7-ZD6KQ6_6yA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Logical WAL streaming & START_REPLICATION (Dave Cramer <pg@fastcrypt.com>) |
| Ответы |
Re: Logical WAL streaming & START_REPLICATION
|
| Список | pgsql-jdbc |
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 controlhttps://github.com/pgjdbc/pgjdbc/blob/ 1be8a9ebafbfbcff118385a61a3507 45addcaf3d/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.
В списке pgsql-jdbc по дате отправления: