0Pricing
PostgreSQL Performance & Query Optimization · 课时

调整 WAL 与检查点以优化数据导入

调整 WAL 设置并使用未记录表，在不发生 I/O 堵塞的情况下维持高写入速率。

调整 WAL 与检查点以优化数据导入 是 CoddyKit 上的免费 PostgreSQL Performance & Query Optimization 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 PostgreSQL Performance & Query Optimization 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 PostgreSQL Performance & Query Optimization 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why WAL Matters for Ingestion

Every change you commit in PostgreSQL is first written to the Write-Ahead Log (WAL) before the data files are updated. This guarantees durability and crash recovery, but during heavy bulk loads the WAL becomes a major source of I/O.

  • Each INSERT or COPY generates WAL records.
  • Periodically a checkpoint flushes dirty pages from shared buffers to disk.
  • If checkpoints fire too often, you pay double I/O and get stalls.

Tuning WAL and checkpoint behaviour is the key to sustaining high write rates without I/O spikes.

Inspecting Current WAL Settings

Before changing anything, look at what your server is running with. The relevant knobs live in pg_settings and can be queried with SHOW.

The most important ingestion-related parameters are max_wal_size, checkpoint_timeout, checkpoint_completion_target, and wal_compression.

SELECT name, setting, unit
FROM pg_settings
WHERE name IN (
  'max_wal_size',
  'min_wal_size',
  'checkpoint_timeout',
  'checkpoint_completion_target',
  'wal_compression'
);

Raising max_wal_size

A checkpoint is triggered either by checkpoint_timeout elapsing or by WAL volume reaching max_wal_size. During a big load the default (often 1 GB) is hit constantly, forcing checkpoint after checkpoint.

  • Raising max_wal_size lets WAL accumulate longer between checkpoints.
  • Fewer checkpoints means dirty pages get coalesced and written once instead of repeatedly.

For an ingestion window, values like 8–32 GB are common.

ALTER SYSTEM SET max_wal_size = '16GB';
SELECT pg_reload_conf();

Spreading Checkpoint I/O

checkpoint_completion_target controls how much of the interval PostgreSQL uses to spread out the checkpoint writes. A value of 0.9 means the writes are smeared across 90% of the time until the next checkpoint, avoiding a sharp I/O burst.

Combined with a longer checkpoint_timeout, this turns spiky checkpoint storms into a smooth, sustained write stream.

ALTER SYSTEM SET checkpoint_timeout = '30min';
ALTER SYSTEM SET checkpoint_completion_target = 0.9;
SELECT pg_reload_conf();

Compressing WAL Records

When full-page images are written after a checkpoint (the first modification of a page), they bloat the WAL. wal_compression compresses those full-page images, trading a little CPU for substantially less WAL volume and disk I/O.

  • On modern PostgreSQL you can choose the algorithm, e.g. lz4 or zstd.
  • Less WAL written also means faster replication and fewer checkpoints from the size trigger.
ALTER SYSTEM SET wal_compression = 'lz4';
SELECT pg_reload_conf();

Unlogged Tables: Skip the WAL Entirely

An unlogged table writes no WAL at all. For staging tables in an ETL pipeline this can dramatically increase throughput, because you bypass the single biggest write cost.

  • Data is still written to disk, but not durably logged.
  • Trade-off: the table is truncated automatically after a crash and is not replicated to standbys.

Perfect for re-buildable staging data; never for the system of record.

CREATE UNLOGGED TABLE staging_events (
  id        bigint,
  payload   jsonb,
  loaded_at timestamptz DEFAULT now()
);

The Staging-to-Final Pattern

A robust ETL design loads raw rows into a fast unlogged staging table, transforms them, then moves the cleaned result into the durable final table.

  • The bulk COPY hits the unlogged table at full speed.
  • The final INSERT ... SELECT writes WAL only once, for validated data.

You get speed where durability does not matter and safety where it does.

INSERT INTO events (id, payload, loaded_at)
SELECT id, payload, loaded_at
FROM staging_events
WHERE payload IS NOT NULL;

TRUNCATE staging_events;

Promoting an Unlogged Table

If a staging table needs to become durable after the load completes, you can convert it in place instead of copying rows. Setting it to LOGGED rewrites the table and begins WAL-logging it.

  • The conversion itself generates WAL for the whole table, so do it once at the end.
  • Going back to UNLOGGED before the next load avoids per-row WAL again.
ALTER TABLE staging_events SET LOGGED;

COPY Beats Row-by-Row INSERT

Even with WAL tuned, how you load matters. COPY batches rows into far fewer, larger WAL records than thousands of individual INSERT statements, and avoids per-statement parse and plan overhead.

Combine COPY with an unlogged staging table and you reach the highest sustainable ingest rate.

COPY staging_events (id, payload)
FROM '/data/events.csv'
WITH (FORMAT csv, HEADER true);

Monitoring Checkpoint Pressure

To know whether your tuning worked, watch the checkpoint statistics. The key signal is the ratio of requested (size-triggered) checkpoints to timed ones.

  • Many requested checkpoints means max_wal_size is still too small for your load.
  • Mostly timed checkpoints means WAL volume is comfortably within budget.

In newer versions these counters live in pg_stat_checkpointer; older versions use pg_stat_bgwriter.

SELECT num_timed, num_requested,
       buffers_written, write_time, sync_time
FROM pg_stat_checkpointer;

Resetting After the Load

Aggressive ingestion settings are great during a load window but waste recovery time and disk afterwards. Once the batch finishes, restore conservative values and force a clean checkpoint so the next crash recovery is fast.

  • Lower max_wal_size and checkpoint_timeout back to steady-state values.
  • Run a manual CHECKPOINT to flush everything immediately.
ALTER SYSTEM SET max_wal_size = '2GB';
ALTER SYSTEM SET checkpoint_timeout = '5min';
SELECT pg_reload_conf();
CHECKPOINT;

Quick Check

You are bulk-loading 200 million rows into a re-buildable staging table that will be validated and copied into the durable table afterward. Which choice most directly reduces WAL write volume during the load?

Recap

To sustain high write rates without I/O stalls:

  • Raise max_wal_size and checkpoint_timeout so checkpoints fire less often, and set checkpoint_completion_target near 0.9 to spread the writes.
  • Enable wal_compression to shrink full-page images.
  • Use UNLOGGED staging tables to skip WAL for re-buildable data, then move validated rows into the durable table.
  • Prefer COPY over row-by-row inserts.
  • Monitor pg_stat_checkpointer for requested-vs-timed checkpoints, and reset conservative values after the load.

常见问题解答

「调整 WAL 与检查点以优化数据导入」课时是免费的吗？

是的 — 「调整 WAL 与检查点以优化数据导入」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 PostgreSQL Performance & Query Optimization 课程的其余内容，请升级到 CoddyKit PRO。 PostgreSQL Performance & Query Optimization 课程共包含 4 节课。

「调整 WAL 与检查点以优化数据导入」这节课中我会学到什么？

调整 WAL 设置并使用未记录表，在不发生 I/O 堵塞的情况下维持高写入速率。 你通过在浏览器中直接运行的动手代码来练习 PostgreSQL Performance & Query Optimization，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 PostgreSQL Performance & Query Optimization 需要有经验吗？

无需任何先前经验。CoddyKit 上的 PostgreSQL Performance & Query Optimization 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。

「调整 WAL 与检查点以优化数据导入」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 PostgreSQL Performance & Query Optimization 课中编写并运行代码吗？

能。每节 PostgreSQL Performance & Query Optimization 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. COPY 与多行 INSERT 的吞吐量
  2. 导入期间延后建立索引与约束
  3. 调整 WAL 与检查点以优化数据导入
  4. 使用 ON CONFLICT 实现大规模插入或更新
← 返回 PostgreSQL Performance & Query Optimization