Sets the planner's assumption about the effective size of the disk cache that is available to a single query. This is factored into estimates of the cost of using an index; a higher value makes it more likely index scans will be used, a lower value makes it more likely sequential scans will be used. When setting this parameter you should consider both PostgreSQL's shared buffers and the portion of the kernel's disk cache that will be used for PostgreSQL data files, though some data might exist in both places. Also, take into account the expected number of concurrent queries on different tables, since they will have to share the available space. This parameter has no effect on the size of shared memory allocated by PostgreSQL, nor does it reserve kernel disk cache; it is used only for estimation purposes. The system also does not assume data remains in the disk cache between queries. If this value is specified without units, it is taken as blocks, that is
BLCKSZ bytes, typically 8kB. The default is 4 gigabytes (
BLCKSZ is not 8kB, the default value scales proportionally to it.)
- Re: Zedstore - compressed in-core columnar storage
- Missing constant propagation in planner on hash quals causes join slowdown
- Re: Connections dropping while using Postgres backend DB with Ejabberd
- Connections dropping while using Postgres backend DB with Ejabberd
- Re: Reinitialize stack base after fork (for the benefit of rr)?