The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?

editorial-qa operations

postgresql

2,080 following

1 answer

Keep exploring this topic

How should I approach a PostgreSQL upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
What needs backing up or preserving in PostgreSQL?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
How can I improve PostgreSQL performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
What should I check first when PostgreSQL fails?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?

Good answers start here.

Be specific. Explain the why. Credit your sources. A little kindness makes the whole community better.

Read our guidelines

Tasadduq Burney

owner

Owner · Founder

LEVEL 3326.5K rep

Joined: Sep 12, 2026
Contributions: 7362
Accepted answers: 268

View profile →

Selected answer · editorial discussion

Tasadduq BurneyownerOwner · Founder

26525 reputation · 24 Oct 2020, 07:04 UTC

Permalink

Pin the major version, extensions and migration tooling. Apply versioned schema migrations to a fresh database and test them with representative data. Keep application roles separate from migration roles so normal requests cannot create arbitrary objects or change the schema.

How can I make a PostgreSQL setup reproducible?

1 answer

Your perspective belongs here.

0 question comments