A New Collection of Thoughtful Learning Apps — Now Available on iOS & Android

Image
I’m excited to share a set of mobile apps I’ve recently completed and published on both the Google Play Store and the Apple App Store. These apps are designed with a simple goal in mind: to make meaningful, structured content more accessible, whether you’re studying theology or improving your English vocabulary. 📱 Now Available on Both Platforms All apps are live and available for download: Google Play Developer Page: https://play.google.com/store/apps/dev?id=5835943159853189043 Apple App Store Developer Page: https://apps.apple.com/ca/developer/q-z-l-corp/id1888794100 📖 Theology & Confession Study Apps For those interested in Reformed theology and classical Christian teachings, I’ve developed a series of apps that present foundational texts in a clean, focused reading format: The Belgic Confession Canons of Dort Heidelberg Catechism Westminster Shorter Catechism Each app is designed to provide a distraction-free experience, making it easier to read, reflect, and revisit these im...

PostgreSQL 18.7 Is More Than a Routine Patch: Check Indexes and Backups

PostgreSQL 18.7 Is More Than a Routine Patch: Check Indexes and Backups

PostgreSQL 18.7 arrived on November 12, 2026, alongside updates for the other supported branches. It is tempting to treat a minor release as a binary replacement and restart. This one deserves a more deliberate rollout: the release notes call out security fixes, several index-corruption bugs, and incremental-backup files that should no longer be trusted as the basis for recovery.

This is not a reason to postpone the upgrade. PostgreSQL's own versioning policy recommends running the current minor release for each supported major version, and describes minor upgrades as less risky than continuing to run an old one. The important distinction is that installing 18.7 is only the first step; you must also perform the follow-up checks that apply to your data and backup strategy.

What changed in 18.7?

The PostgreSQL project says the release contains 52 security fixes and more than 140 bug fixes across the supported branches. One security correction affects INSERT ... ON CONFLICT against auto-updatable views: before the fix, a conflict could expose or update a row hidden by the view's WHERE condition. If an application uses a view as a tenant or row-visibility boundary, that is a security concern, not merely an edge-case query result.

The release also changes behavior around several classes of memory-safety, privilege-checking, query-planning, and concurrency problems. Applications do not need a schema dump and restore for a minor upgrade, but extensions written in C deserve attention. The 18.7 notes say that the new composite-type mismatch protection requires rebuilding C-language extensions, and that some extensions may need source changes.

The two operational warnings that should change your rollout

1. Review indexes on bpchar columns

PostgreSQL's bpchar type is the internal type behind CHAR(n). In 18.7, B-tree deduplication is disabled for affected new index entries because trailing-space comparison can make values of different lengths compare equal while still differing byte-for-byte. The release notes warn that existing indexes may already contain problematic entries and specifically recommend rebuilding B-tree indexes on bpchar columns.

First inventory candidate columns and their indexes. This query is intentionally a report, not an automatic repair:

SELECT n.nspname AS schema_name, c.relname AS table_name, a.attname AS column_name, i.relname AS index_name, pg_get_indexdef(i.oid) AS index_definition FROM pg_attribute AS a JOIN pg_class AS c ON c.oid = a.attrelid JOIN pg_namespace AS n ON n.oid = c.relnamespace JOIN pg_index AS ix ON ix.indrelid = c.oid JOIN pg_class AS i ON i.oid = ix.indexrelid WHERE a.atttypid = 'pg_catalog.bpchar'::regtype AND a.attnum > 0 AND NOT a.attisdropped ORDER BY 1, 2, 3, 5;

Review the output with your database owner and migration records. The query can identify indexes whose definition includes a bpchar column, but it does not prove that every index is affected or that an index is corrupt. It is a safe starting point for selecting the indexes that the 18.7 release notes tell you to rebuild.

For a single index, the normal command is:

REINDEX INDEX CONCURRENTLY schema_name.index_name;

CONCURRENTLY avoids taking locks that prevent concurrent inserts, updates, and deletes on the table, but it is not free: it takes longer, uses extra resources, and has additional failure and cleanup considerations. Test the command on a staging copy, watch disk space and replication lag, and schedule the work according to your workload. For a maintenance window, a non-concurrent rebuild may be simpler:

REINDEX INDEX schema_name.index_name;

Do not blindly run REINDEX DATABASE on a busy production system as a substitute for analysis. PostgreSQL documents that a normal reindex blocks writes to the parent table and can block queries that try to use the index. The right scope depends on the release-note condition, your schema, and your availability requirements.

2. Replace incremental-backup starting points

PostgreSQL 18.7 says that several bugs could corrupt incremental backup files and recommends taking a new full backup after updating, then using that full backup as the basis for later incrementals. Treat this as a recovery-plan change, not just a backup-job change.

After upgrading:

  • Complete and record a new full backup from the updated server.
  • Retire the affected incremental chain from your restore runbook rather than assuming it is valid.
  • Run a restore or recovery rehearsal from the new full backup and verify that the recovered service is usable.
  • Keep the old chain according to your retention policy, but label its limitations clearly.
  • Confirm that monitoring reports the new full backup as the parent for subsequent incrementals.

A successful backup command is not evidence that recovery works. The meaningful test is a restore that reaches a known-good point and passes application-level checks.

A focused rollout checklist

  1. Read the release notes for your branch. PostgreSQL 18.7 is the current 18.x release, but the coordinated update also includes 17.12, 16.16, 15.20, and 14.25. Verify the exact version and branch-specific notes before scheduling work.
  2. Inventory extensions and deployment artifacts. Rebuild or update C-language extensions as required, and test generated SQL, migrations, and privilege-sensitive views.
  3. Install the minor update and restart. A minor upgrade does not require a dump/restore; it does require the usual controlled server restart.
  4. Rebuild applicable indexes. Prioritize B-tree indexes on bpchar columns identified during review, and investigate any other release-note entry that names REINDEX.
  5. Create a new full backup. Make it the parent of future incremental backups, then test a restore.
  6. Exercise security boundaries. Test views used for tenant isolation or filtered writes, especially code that uses INSERT ... ON CONFLICT. The fix should prevent an unauthorized result; tests should confirm the intended authorized behavior remains.
  7. Record evidence. Save the installed version, extension versions, index work performed, backup identifier, and restore-test result in the change record.

The practical takeaway

PostgreSQL 18.7 is a good example of why “minor” does not mean “ignore the release notes.” Apply the update promptly, but do not stop at package installation. Review the affected indexes, rebuild the ones that meet the documented condition, establish a new full-backup base, and test security-sensitive views. That small amount of operational discipline turns a patch upgrade into a safer database change.

References

❤️ Support This Blog


If this post helped you, you can support my writing with a small donation. Thank you for reading.


Comments

Popular Posts

A New Collection of Thoughtful Learning Apps — Now Available on iOS & Android

react-native run-android : do not build/update modified code(App.js)