Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

worker.c

Blame
    • Peter Eisentraut's avatar
      fe7bbc4d
      Fix remote position tracking in logical replication · fe7bbc4d
      Peter Eisentraut authored
      We need to set the origin remote position to end_lsn, not commit_lsn, as
      commit_lsn is the start of commit record, and we use the origin remote
      position as start position when restarting replication stream.  If we'd
      use commit_lsn, we could request data that we already received from the
      remote server after a crash of a downstream server.
      
      Author: Petr Jelinek <petr.jelinek@2ndquadrant.com>
      fe7bbc4d
      History
      Fix remote position tracking in logical replication
      Peter Eisentraut authored
      We need to set the origin remote position to end_lsn, not commit_lsn, as
      commit_lsn is the start of commit record, and we use the origin remote
      position as start position when restarting replication stream.  If we'd
      use commit_lsn, we could request data that we already received from the
      remote server after a crash of a downstream server.
      
      Author: Petr Jelinek <petr.jelinek@2ndquadrant.com>