Обсуждение: checkpoint_flush_after and friends
configuration parameters *_flush_after were added in 9.6. They are not in postgresql.conf.sample, but are also not marked GUC_NOT_IN_SAMPLE. Is this intentional and/or desirable?
Cheers,
Jeff
On 2016-11-10 12:13:05 -0800, Jeff Janes wrote: > configuration parameters *_flush_after were added in 9.6. They are not in > postgresql.conf.sample, but are also not marked GUC_NOT_IN_SAMPLE. Is this > intentional and/or desirable? Hm? $ grep flush_after src/backend/utils/misc/postgresql.conf.sample #bgwriter_flush_after = 0 # 0 disables, #backend_flush_after = 0 # 0 disables, default is 0 #wal_writer_flush_after = 1MB # 0 disables #checkpoint_flush_after = 0 # 0 disables, Andres
On Thu, Nov 10, 2016 at 12:17 PM, Andres Freund <andres@anarazel.de> wrote:
On 2016-11-10 12:13:05 -0800, Jeff Janes wrote:
> configuration parameters *_flush_after were added in 9.6. They are not in
> postgresql.conf.sample, but are also not marked GUC_NOT_IN_SAMPLE. Is this
> intentional and/or desirable?
Hm?
$ grep flush_after src/backend/utils/misc/postgresql.conf.sample
#bgwriter_flush_after = 0 # 0 disables,
#backend_flush_after = 0 # 0 disables, default is 0
#wal_writer_flush_after = 1MB # 0 disables
#checkpoint_flush_after = 0 # 0 disables,
Andres
My apologies. I must have gotten my default conf file from the wrong initdb.
Jeff