> On 31 Aug 2016, at 03:28, Craig Ringer wrote:
>
> On 25 Aug. 2016 20:03, "Stas Kelvich" wrote:
> >
> > Thanks for clarification about how restart_lsn is working.
> >
> > Digging slightly deeper into this topic revealed that problem was in two
> > phase decoding, not it logical decoding itself
On 25 Aug. 2016 20:03, "Stas Kelvich" wrote:
>
> > On 20 Aug 2016, at 15:59, Craig Ringer wrote:
> >
> > I'll wait for a test case or some more detail.
>
> Thanks for clarification about how restart_lsn is working.
>
> Digging slightly deeper into this topic revealed that problem was in two
phase
> On 20 Aug 2016, at 15:59, Craig Ringer wrote:
>
> I'll wait for a test case or some more detail.
Thanks for clarification about how restart_lsn is working.
Digging slightly deeper into this topic revealed that problem was in two phase
decoding, not it logical decoding itself.
While I was wri
On 20 August 2016 at 14:56, konstantin knizhnik
wrote:
> Thank you for answers.
>
> No, you don't need to recreate them. Just advance your replication
> identifier downstream and request a replay position in the future. Let the
> existing slot skip over unwanted data and resume where you want to
Thank you for answers.
> No, you don't need to recreate them. Just advance your replication identifier
> downstream and request a replay position in the future. Let the existing slot
> skip over unwanted data and resume where you want to start replay.
>
> You can advance the replication origins
On 20 August 2016 at 00:36, Konstantin Knizhnik
wrote:
>
> Sorry, I have not saved trace with output of logical decoder. Bu t it
> really decodes just one update!
>
That's definitely a worry. Can you turn this into a reproducible, self
contained test case?
> DROP_REPLICATION_SLOT "mtm_slot_1
On 19 August 2016 at 15:34, konstantin knizhnik
wrote:
> Hi,
>
> We are using logical decoding in multimaster and we are faced with the
> problem that inconsistent transactions are sent to replica.
> Briefly, multimaster is using logical decoding in this way:
> 1. Each multimaster node is connect
On 19/08/16 18:36, Konstantin Knizhnik wrote:
On 19.08.2016 19:06, Petr Jelinek wrote:
I don't think this will work correctly, there will be gap between when
the new slot starts to decode and the drop of the old one as the new
slot first needs to make snapshot.
Do I understand correctly that
On 19.08.2016 19:06, Petr Jelinek wrote:
I don't think this will work correctly, there will be gap between when
the new slot starts to decode and the drop of the old one as the new
slot first needs to make snapshot.
Do I understand correctly that you are not using replication origins?
No
On 19/08/16 09:34, konstantin knizhnik wrote:
We are using logical decoding in multimaster and we are faced with the
problem that inconsistent transactions are sent to replica.
Briefly, multimaster is using logical decoding in this way:
1. Each multimaster node is connected with each other using
Hi,
We are using logical decoding in multimaster and we are faced with the problem
that inconsistent transactions are sent to replica.
Briefly, multimaster is using logical decoding in this way:
1. Each multimaster node is connected with each other using logical decoding
channel and so each pair
11 matches
Mail list logo
