Articles

Dev matches staging. Staging matches production. Then a deploy fails on a column nobody remembers adding. Here's how to check every environment against production in one run.

Read more →

PostgresCompare's MCP server support lets AI assistants like Claude explore your databases, compare schemas, and generate migration scripts—all through natural conversation.

Read more →

We’ve completely rewritten the PostgresCompare CLI. With support for over 40 object types, Git-integrated comparisons, and CI/CD-ready output formats, it's the ultimate tool for automating your PostgreSQL schema workflows.

Read more →

Comparing database schemas is a core task. We review 5 methods, from simple CLI tricks to dedicated tools, to find the best fit for your workflow.

Read more →

Both tools compare PostgreSQL schemas. One deploys directly with safety checks and runs 100% locally. See the full feature and pricing comparison.

Read more →

Learn three ways to compare PostgreSQL databases: using a dedicated comparison tool, pgAdmin Schema Diff, or pg_dump. Find schema differences in minutes, not hours.

Read more →

pgAdmin is free but limited. PostgresCompare offers deployment scripts, comparison history, and 40+ object types. See the full feature comparison.

Read more →

Renaming a column sounds simple, but on a live system it can break your application instantly. Here's how to do it safely without downtime.

Read more →

DROP TABLE and DROP COLUMN can destroy data instantly. A reference guide to destructive PostgreSQL operations, their risks, and safer alternatives.

Read more →

From first launch to a deployment script in six steps — try the demo, connect your databases, compare them, and generate the SQL to bring them in sync.

Read more →

While exploring the pg_catalog schema I noticed that while the relationships between the tables are documented, they are not enforced by actual database constraints. Tom Lane provided an excellent answer as to why this is the case:

Read more →

The CREATE DATABASE statement is used to create a new PostgreSQL database. It does so by cloning an existing database, a template. PostgreSQL comes with two template databases, template0 and template1. The difference between template0 and template1 is their intended use. template1 is the default template when creating a new database, it can also be connected to and any custom objects that new databases should have can be created there. template0 does not accept connections and is therefore a clean source for those times when template1 has become messy for some reason.

Read more →

I believe that while listening to customer feedback and giving the people what they want can be of great benefit to the short term development of an application, it is also important to lay out some key principles that really define the essence of the product. Key principles help in many ways. From a users point of view the application has an identity and a unique look and feel. Internally the principles can be used as a guide for decision making.

Read more →

A question came up on the pgsql-general mailing list regarding how to obtain column information from a PostgreSQL database. Finding the definition of database objects is something I spend a lot of time doing when working on the comparison and scripting engines for Postgres Compare.

Read more →

There was a question recently on pgsql-general about Stored procedure version control. The question was:

Read more →