Skip to main content

12 posts tagged with "postgres"

View All Tags

Your Software Factory Stops at the Database

· 11 min read
Ariel Mashraki
Building Atlas

In August, I wrote that the AI-native SDLC playbook stops at the database. Code is cheap to regenerate. The data in your production database isn't. Software factories make this sharper. An agent takes a ticket, writes the code, runs the tests, and ships it, with no human in the loop. That works for code because code has gates. Tests say whether it's correct, and a bad deploy rolls back.

A migration has no such gate. It can pass every test and still lock your largest table for minutes, because what it costs depends on the data, not the code. Today, the gate is a person who reads the migration and knows which tables are big. A factory doesn't have that person.

In this post, I'll show how we close that gap in Atlas. The team writes down what database code may cost: migrations, queries, functions, procedures, and triggers. Atlas measures every agent's change against those limits twice, first on synthetic data in the agent's sandbox, then on a masked production snapshot before deploy.

Atlas v1.4: Security Scanning, Database Profiler, Agent Skills, Drift Detection, and More

· 37 min read
Ariel Mashraki
Building Atlas

Hey everyone!

We're excited to announce Atlas v1.4. This release brings security scanning to your databases: the new atlas security scan command reports the CVEs affecting your database servers and extensions, from the CLI, CI, or Kubernetes. It also introduces agent skills, a profiler for the Atlas testing framework that works on production-like data, and drift checks between deployments.

Here is what you can find in this release:

  • Security Scanning for Databases - Vulnerability detection for your database servers and extensions with atlas security scan, from CI to Kubernetes, and blast-radius checks for roles.
  • Atlas Agent Skills - Teach Claude Code, Codex, Cursor, and GitHub Copilot to plan, lint, and test schema changes with Atlas.
  • Profiler for the Testing Framework - Measure the locks, rewrites, and space of migrations, queries, and database code, over a masked Amazon RDS snapshot, CSV files, or synthetic rows. In preview.
  • Drift Detection Between Deployments - atlas migrate drift reports every object that diverged from your migrations, for one database or every tenant.
  • Schema Repositories in Your Own Storage - Store schema repositories in your own S3, GCS, or Azure Blob Storage bucket, or an OCI registry, instead of Atlas Cloud.
  • Database Driver Improvements - Snowflake governance policies, SQL Server linked servers and filegroups, PostgreSQL temporal keys, Databricks metric views, Redshift datashares, and more.
  • Atlas Binaries Are Moving to atlasbinaries.com - Starting December 2026, release.ariga.io redirects to atlasbinaries.com. Direct downloads only need the new hostname.

PostgreSQL 19: Security Changes and Preparing with Atlas

· 13 min read
Noa Rogoszinski
DevRel Engineer

PostgreSQL 19 is scheduled for general availability on November 19, 2026, one week after PostgreSQL 14 reaches end of life on November 12. From then on, servers on PostgreSQL 14 get no more security fixes. Versions 15 through 18 are still supported, but version 19 will be supported the longest, into late 2031.

This post covers what version 19 changes for security and the schema objects that block an upgrade to it, and how to use the week before GA to prepare with Atlas: scan your servers for their versions and CVEs, keep upgrade blockers out with schema rules, and apply the same schema, roles, and grants to the new instance from code.

DACPAC for PostgreSQL: Where Atlas Fills the Gap

· 14 min read
Noa Rogoszinski
DevRel Engineer

If you've searched for "DACPAC for PostgreSQL," you already know the answer: there isn't one. DACPAC is a Microsoft file format, built into SQL Server Data Tools and deployed with SqlPackage, and it has no equivalent outside the SQL Server ecosystem. What you're actually looking for isn't the file format, it's the workflow: define the schema once, let the tool diff it against a live database, and deploy the result without hand-written migration scripts. Atlas gives you that workflow for PostgreSQL.

Atlas v1.3: Security Graph for Databases, Atlas Scripts, the atlas cloud Command, and More

· 29 min read
Ariel Mashraki
Building Atlas

Hey everyone!

We're excited to announce Atlas v1.3. This release delivers on a promise we made in v1.2: the security graph is now live in Atlas Cloud, mapping your entire database attack surface. It also introduces Atlas Scripts for running data operations as code, safer and faster migrations, and a new command group for working with the Atlas Registry from the CLI.

Here is what you can find in this release:

  • Security Graph for Databases - Map your entire database attack surface: permissions, misconfigurations, and CVEs across every object, with severity tiers and blast-radius tracing.
  • Atlas Scripts: DataOps as Code - Backfills, GDPR purges, and reports declared as code: transactional mutations, masked queries, and batched loops, reviewed and tested in CI.
  • atlas cloud: Manage Registry Resources from the CLI - Repositories, databases, and deployment history from the terminal, with JSON output for scripts, CI gates, and AI agents, plus security graph and lineage graph exports.
  • Schema Annotations - Attach type-safe metadata to schema resources and render GraphQL, OpenAPI, or any other format from it with templates.
  • Pre-Apply Drift Detection - Block a deployment when the database drifted from the expected state, with the diff printed before any statement runs.
  • Database Driver Improvements - Lock-safe NOT NULL and 8x-10x faster schema tests on PostgreSQL, Oracle roles and storage, Snowflake Iceberg tables, ClickHouse row policies, and more.
  • Simpler Licensing and No AI Training - One agreement replaces the separate EULA and SaaS terms, with a written commitment that we never train AI models on your data.

Testing PostgreSQL Schemas with pgTAP and Atlas

· 7 min read
Noa Rogoszinski
DevRel Engineer

Testing your database schema shouldn't be an afterthought. Automating checks on your objects, constraints, and functions is critical to catching breaking changes before they hit production.

Enter pgTAP—which relies on traditional runtime assertions in an ephemeral database—and Atlas—which leverages a modern, declarative approach. This post breaks down how both tools handle schema testing and explains when you should swap out heavy runtime assertions for Atlas's lightweight lint rules.

Atlas v1.2: Column-Level Lineage, Registry Backup Storage, Schema Ownership Policy, and More

· 7 min read
Ariel Mashraki
Building Atlas

Hey everyone!

We're excited to announce Atlas v1.2. This release brings column-level data lineage to Atlas Cloud, registry backups to your own cloud storage, a schema ownership policy for CI, and expanded database coverage.

Here is what you can find in this release:

  • Column-Level Data Lineage - Trace how columns are derived from upstream sources across tables, views, and datasets in Atlas Cloud.
  • Offline Access & Registry Backups - Back up Atlas Registry repositories to S3, GCS, or Azure Blob Storage. Atlas Pro license grants are cached in CI/CD environments, so your pipeline never has a single point of failure.
  • Schema Ownership Policy - Enforce which GitHub users and teams can modify specific schema objects, closing the gap between CODEOWNERS and DDL access control.
  • Database Driver Improvements - PostgreSQL routine permissions, user-mapping, and default ACLs; Snowflake tasks and pipes; Oracle UDTs; Expanded permissions for MSSQL, MySQL, and ClickHouse.

Tame Complex PostgreSQL Schemas with Atlas, a Terraform for Databases

· 7 min read
Rotem Tamir
Building Atlas

As applications grow, their underlying database schemas inevitably grow more complex. What often starts as an afterthought handled by a single developer quickly turns into a critical, high-risk responsibility that demands precision and discipline.

Tools like Flyway and Liquibase automate the application of schema changes, but they stop short of addressing the real pain points: planning and validating those changes before they hit production. These steps remain largely manual, error-prone, and disliked by most developers.

Atlas is designed to fill this gap by automating the entire lifecycle of schema changes. Inspired by Terraform, Atlas provides a declarative approach to database schema management, enabling teams to define their schemas as code and automate the planning, validation, and application of changes.

Why Terraform for Databases?​

Infrastructure teams have standardized on tools like Terraform to manage cloud resources declaratively. Databases, despite being critical infrastructure, often remain outside this workflow. Schema changes are still handled manually or with ad-hoc migration scripts, leading to drift, unpredictability, and production risks.

Announcing v0.17: Triggers and Improved ERDs

· 6 min read
Rotem Tamir
Building Atlas

Hi everyone,

I hope you are enjoying the holiday season, because we are here today with the first Atlas release of 2024: v0.17. It's been only a bit over a week since our last release, but we have some exciting new features we couldn't wait to share with you:

  • Trigger Support - Atlas now supports managing triggers on MySQL, PostgreSQL, MariaDB and SQLite databases.
  • Improved ERDs - You can now visualize your schema's SQL views, as well as create filters to select the specific database objects you wish to see.

Without further ado, let's dive in!