How to use the configuration parameter checkpoint_flush_after of PostgreSQL

This article focuses on "how to use the PostgreSQL configuration parameter checkpoint_flush_after", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to use the configuration parameter checkpoint_flush_after of PostgreSQL.

Try 0/256kB/2MB with sysbench testing under CentOS 7.x, with only negligible nuances.

-- checkpoint_flush_after = 2MB--SQL statistics: queries performed: read: 107367 write: 111268 other: 16840 total: 235475 transactions: 8419 (84.16 per sec.) Queries: 235475 (2353.96 per sec.) Ignored errors: 43 (0.43 per sec.) Reconnects: 0 (0.00 per sec.) Throughput: events/s (eps): 84.1616 time elapsed: 100.0337s total number of events: 8419Latency (ms): min: 2.56 Avg: 23.76 max: 311.66 95th percentile: 62.19 sum: 200002.13Threads fairness: events (avg/stddev): 4209.5000 execution time ( Avg/stddev): 100.0011/0.00--checkpoint_flush_after = 256kB--SQL statistics: queries performed: read: 110021 write: 114168 other: 17072 total: 241261 transactions: 8535 (85.31 per sec. Queries: 241261 (2411.50 per sec.) Ignored errors: 29 (0.29 per sec.) Reconnects: 0 (0.00 per sec.) Throughput: events/s (eps): 85.3106 time elapsed: 100.0462s total number of events: 8535Latency (ms): min: 2.62 Avg: 23.43 max: 260.37 95th percentile: 61.08 sum: 200017.57Threads fairness: events (avg/stddev): 4267.5000 execution time ( Avg/stddev): 100.0088/0.02--checkpoint_flush_after = 0--SQL statistics: queries performed: read: 111431 write: 115279 other: 17380 total: 244090 transactions: 8689 (86.86 per sec. Queries: 244090 (2440.19 per sec.) Ignored errors: 42 (0.42 per sec.) Reconnects: 0 (0.00 per sec.) Throughput: events/s (eps): 86.8646 time elapsed: 100.0293s total number of events: 8689Latency (ms): min: 2.60 Avg: 23.02 max: 213.39 95th percentile: 59.99 sum: 199980.96Threads fairness: events (avg/stddev): 4345000 execution time 16.50 ( Avg/stddev): 99.9905 Compact 0.00 to here I believe you have a deeper understanding of "how to use the configuration parameter checkpoint_flush_after of PostgreSQL", so you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!