[BUG] PostgreSQL 18: ERROR: column "checkpoint_write_time" does not exist

[pommetjehorlepiep]

Description

PostgreSQL logs show following error when running LibreDB (monitoring: performance)

2026-09-14 12:28:55.418 AEST [99] ERROR:  column "checkpoint_write_time" does not exist at character 31
2026-09-14 12:28:55.418 AEST [99] STATEMENT:
SELECT
checkpoint_write_time,
checkpoint_sync_time
FROM pg_stat_bgwriter

Steps to Reproduce

1. PostgreSQL database version 18 running
2. postgresql.conf contains: shared_preload_libraries = 'pg_stat_statements'
3. Database restarted!
4. pg_stat_statements extension created in the database you connect to (ie: you ran CREATE EXTENSION pg_stat_statements;)
5. Monitor PostgreSQL log

Expected Behavior

Mentioned error should not be popping up if database connected to has got extension configured + create command has been run.

Actual Behavior

Mentioned error pops up when actively monitoring performance

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

Please provide the following information:

• LibreDB Studio Version: 0.15.0
• Browser: Version 0.17.0.1 (Official Build, Chromium 153.0.8010.36) stable (x86_64)
• OS: Alpine 3.24 (container)
• Node.js/Bun Version: Node.js: 24.18.1
• Database Type: Postgres
• Database Version: PostgreSQL 18.6

Additional Context

Add any other context about the problem here.

Possible Solution

See DataDog/integrations-core#19685
It looks like there were column changes in Postgres >=17 which are not accounted for.

Logs

If applicable, add relevant logs or error messages:

2026-09-14 12:47:55.852 AEST [204] ERROR:  column "checkpoint_write_time" does not exist at character 31
2026-09-14 12:47:55.852 AEST [204] STATEMENT:
SELECT
checkpoint_write_time,
checkpoint_sync_time
FROM pg_stat_bgwriter

[cevheri]

Thanks for the report, @pommetjehorlepiep, and for the log lines. Confirmed and fixed in #832.

The cause is the one you pointed at: PostgreSQL 17 moved the checkpoint timings from pg_stat_bgwriter to pg_stat_checkpointer, and the monitoring code still read the old view. On 17 and 18 that logged the error on every refresh and left the checkpoint time on the Performance tab showing "N/A".

The provider now checks which view the server has and reads that one. I measured it against PostgreSQL 14 through 18, including 18 with pg_stat_statements preloaded as in your setup: every version reports a value and none logs the error.

One note for anyone landing here: pg_stat_statements is not needed to reproduce this. The error comes from the checkpoint query alone.

This issue will close when #832 is merged, and the fix ships in the next release.