Revert "Auto-tune effective_cache size to be 4x shared buffers"
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 9 May 2014 00:49:38 +0000 (20:49 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 9 May 2014 00:49:38 +0000 (20:49 -0400)
commita16d421ca4fc639929bc964b2585e8382cf16e33
treec67fe19b554dc2da53cbacc0349ce58ac2bf8514
parent08c8e8962f56c23c6799178d52d3b31350a0708f
Revert "Auto-tune effective_cache size to be 4x shared buffers"

This reverts commit ee1e5662d8d8330726eaef7d3110cb7add24d058, 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.
doc/src/sgml/config.sgml
src/backend/optimizer/path/costsize.c
src/backend/utils/misc/guc-file.l
src/backend/utils/misc/guc.c
src/backend/utils/misc/postgresql.conf.sample
src/include/optimizer/cost.h
src/include/utils/guc.h
src/test/regress/expected/join.out
src/test/regress/sql/join.sql