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

backend

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Peter Eisentraut authored
    This happens when we add a replica identity column on a subscriber
    that does not yet exist on the publisher, according to the mapping
    maintained by the subscriber.  Code that checks whether the target
    relation on the subscriber is updatable would check the replica
    identity attribute bitmap with a column number -1, which would result
    in an error.  To fix, skip such columns in the bitmap lookup and
    consider the relation not updatable.  The result is consistent with
    the rule that the replica identity columns on the subscriber must be a
    subset of those on the publisher, since if the column doesn't exist on
    the publisher, the column set on the subscriber can't be a subset.
    
    Reported-by: default avatarTim Clarke <tim.clarke@minerva.info>
    Analyzed-by: default avatarJehan-Guillaume de Rorthais <jgdr@dalibo.com>
    Discussion: https://www.postgresql.org/message-id/flat/a9139c29-7ddd-973b-aa7f-71fed9c38d75%40minerva.info
    7961da18
    History
    Name Last commit Last update
    ..