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

postgresql.conf.sample

Blame
    • Tom Lane's avatar
      a16d421c
      Revert "Auto-tune effective_cache size to be 4x shared buffers" · a16d421c
      Tom Lane authored
      This reverts commit ee1e5662, as well as
      a remarkably large number of followup commits, which were mostly concerned
      with the fact that the implementation didn't work terribly well.  It still
      doesn't: we probably need some rather basic work in the GUC infrastructure
      if we want to fully support GUCs whose default varies depending on the
      value of another GUC.  Meanwhile, it also emerged that there wasn't really
      consensus in favor of the definition the patch tried to implement (ie,
      effective_cache_size should default to 4 times shared_buffers).  So whack
      it all back to where it was.  In a followup commit, I'll do what was
      recently agreed to, which is to simply change the default to a higher
      value.
      a16d421c
      History
      Revert "Auto-tune effective_cache size to be 4x shared buffers"
      Tom Lane authored
      This reverts commit ee1e5662, as well as
      a remarkably large number of followup commits, which were mostly concerned
      with the fact that the implementation didn't work terribly well.  It still
      doesn't: we probably need some rather basic work in the GUC infrastructure
      if we want to fully support GUCs whose default varies depending on the
      value of another GUC.  Meanwhile, it also emerged that there wasn't really
      consensus in favor of the definition the patch tried to implement (ie,
      effective_cache_size should default to 4 times shared_buffers).  So whack
      it all back to where it was.  In a followup commit, I'll do what was
      recently agreed to, which is to simply change the default to a higher
      value.