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

pgarch.c

  • Bruce Momjian's avatar
    12e67820
    > I enclose a short patch to reduce the PGARCH_RESTART_INTERVAL from 60 · 12e67820
    Bruce Momjian authored
    > seconds to 10 seconds. The original number was plucked from thin air
    > some months ago, and I'd like to review that now based upon further
    > thought, observation and experience.
    >
    > This change has little or no effect on performance, since the interval
    > is there mainly to avoid repeated respawn attempts if archiver fails at
    > startup. Archiver start-up time is very quick, so there is little danger
    > of exceeding 10 seconds.
    >
    > On a busy system, if the archiver does die, then many files can build up
    > in the 60 seconds before respawning. That xlog file backlog could take
    > some time to clear. This then leaves a larger than normal window of data
    > loss for a possibly long period.
    >
    > It's a minor change only, with no other effect on function.
    
    Simon Riggs
    12e67820
    History
    > I enclose a short patch to reduce the PGARCH_RESTART_INTERVAL from 60
    Bruce Momjian authored
    > seconds to 10 seconds. The original number was plucked from thin air
    > some months ago, and I'd like to review that now based upon further
    > thought, observation and experience.
    >
    > This change has little or no effect on performance, since the interval
    > is there mainly to avoid repeated respawn attempts if archiver fails at
    > startup. Archiver start-up time is very quick, so there is little danger
    > of exceeding 10 seconds.
    >
    > On a busy system, if the archiver does die, then many files can build up
    > in the 60 seconds before respawning. That xlog file backlog could take
    > some time to clear. This then leaves a larger than normal window of data
    > loss for a possibly long period.
    >
    > It's a minor change only, with no other effect on function.
    
    Simon Riggs