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

tar.c

Blame
    • Magnus Hagander's avatar
      56c7d8d4
      Allow pg_basebackup to stream transaction log in tar mode · 56c7d8d4
      Magnus Hagander authored
      This will write the received transaction log into a file called
      pg_wal.tar(.gz) next to the other tarfiles instead of writing it to
      base.tar. When using fetch mode, the transaction log is still written to
      base.tar like before, and when used against a pre-10 server, the file
      is named pg_xlog.tar.
      
      To do this, implement a new concept of a "walmethod", which is
      responsible for writing the WAL. Two implementations exist, one that
      writes to a plain directory (which is also used by pg_receivexlog) and
      one that writes to a tar file with optional compression.
      
      Reviewed by Michael Paquier
      56c7d8d4
      History
      Allow pg_basebackup to stream transaction log in tar mode
      Magnus Hagander authored
      This will write the received transaction log into a file called
      pg_wal.tar(.gz) next to the other tarfiles instead of writing it to
      base.tar. When using fetch mode, the transaction log is still written to
      base.tar like before, and when used against a pre-10 server, the file
      is named pg_xlog.tar.
      
      To do this, implement a new concept of a "walmethod", which is
      responsible for writing the WAL. Two implementations exist, one that
      writes to a plain directory (which is also used by pg_receivexlog) and
      one that writes to a tar file with optional compression.
      
      Reviewed by Michael Paquier