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

commands

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    in the current backend for the target table.  These operations move tuples
    around and would thus invalidate the TIDs stored in the trigger event records.
    (We need not worry about events in other backends, since acquiring exclusive
    lock should be enough to ensure there aren't any.)  It might be sufficient
    to forbid only the table-rewriting variants of ALTER TABLE, but in the absence
    of any compelling use-case, let's just be safe and simple.  Per follow-on
    investigation of bug #3847, though this is not actually the same problem
    reported therein.
    
    Possibly this should be back-patched, but since the case has never been
    reported from the field, I didn't bother.
    20e86215
    History
    Name Last commit Last update
    ..