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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    explicit paths, so that the log can be replayed in a data directory
    with a different absolute path than the original had.  To avoid forcing
    initdb in the 8.0 branch, continue to accept the old WAL log record
    types; they will never again be generated however, and the code can be
    dropped after the next forced initdb.  Per report from Oleg Bartunov.
    We still need to think about what it really means to WAL-log CREATE
    TABLESPACE commands: we more or less have to put the absolute path
    into those, but how to replay in a different context??
    cad86e25
    History
    Name Last commit Last update