Bytebase is HIPAA-compliant — independent verification that our administrative, physical, and technical safeguards meet the HIPAA Security Rule for handling Protected Health Information.

HIPAA Compliance

PAM tools gate connections; databases also need SQL review, schema change workflow, and statement-level approval. Why most teams use PAM with Bytebase.

Bytebase vs. PAM: Why Database Teams Need More Than Privileged Access Management

The difference between 'audit logging enabled' and 'audit evidence your SOC 2 auditor will accept' — what we learned going through our own SOC 2 audit, and what we built in response.

What SOC 2 Taught Us About Database Audit Logs

Bytebase vs. Atlas compared across migration approach, CI/CD, access control, and pricing. Updated for Atlas v1.1 and Bytebase 3.16.

Bytebase vs. Atlas: a side-by-side comparison for database schema migration

Best practices for database access control covering least privilege, RBAC, just-in-time access, and compliance with SOC 2, HIPAA, and GDPR.

Database Access Control Best Practices

SOX Section 404 requires IT general controls over database changes. Learn the ITGC domains, six audit questions teams fail, and how to build SOX-ready controls

Database Change Management for SOX Compliance

TRUNCATE and DELETE both remove rows, but they differ in speed, rollback behavior, and locking. Compare how they work in PostgreSQL, MySQL, and SQL Server.

TRUNCATE vs DELETE in SQL: Differences Across PostgreSQL, MySQL, and SQL Server

Six database design patterns for production systems: normalization, star schema, EAV, polymorphic associations, multi-tenancy, and anti-patterns.

Database Design Patterns Every Developer Should Know

pgvector adds vector storage and similarity search to PostgreSQL. Learn how to install it, query embeddings, build indexes, and decide when it is enough.

pgvector: How to Add Vector Search to PostgreSQL

Upsert inserts or updates a row based on key conflicts. Learn MySQL INSERT ON DUPLICATE KEY UPDATE, PostgreSQL ON CONFLICT, and SQL Server MERGE.

Upsert in SQL: INSERT ON DUPLICATE KEY vs ON CONFLICT Explained

How codifying the full database development lifecycle — not just DDL — empowers LLMs and AI Agents.

From Schema as Code to Schema as Context

Learn how to find and fix slow MySQL queries using the slow query log, EXPLAIN, index tuning, and query rewrites, with practical examples for each.

How to Fix Slow MySQL Queries: A Practical Guide

A detailed comparison of Convex and Supabase covering architecture, real-time capabilities, data model, pricing, and schema management to help you choose.

Convex vs Supabase: Which Backend Platform Should You Choose?

Blue-green deployments work cleanly for stateless apps. Databases are stateful. Learn what makes database blue-green deployments hard and how to do them safely.

Database Blue-Green Deployment: A Practical Guide

The 10 best data management tools in 2026 — database GUI clients, schema migration tools, data pipelines, and analytics platforms compared with pricing.

Top 10 Data Management Tools in 2026

A practical guide to governing AI agent access to enterprise databases — covering authentication, authorization, query control, audit logging, and data masking.

How to Govern AI Agent Access to Enterprise Data

Postgres-only SQL editors are designed specifically for Postgres databases, providing a more focused and efficient experience for Postgres users. In this post, we are taking a look at the top Postgres-only SQL editors in 2026.

Enterprise Text-to-SQL: Context, Evaluation, and Governance for Consistent Results

Database deployment tools for devops teams in 2026.

Database Deployment Tools for DevOps Teams in 2026

Schema change detection and notification are essential for data pipelines. This article explains why a simple column rename can break your data pipeline and how to prevent it.

Schema Change Detection and Notification: Why a Simple Column Rename Can Break Your Data Pipeline

A comprehensive guide to understanding and analyzing Postgres query plans.

Postgres Query Plan: How to Read and Fix Performance Issues

This article explores the anatomy of Postgres permissions ERROR 42501.

The Anatomy of Postgres Permission ERROR 42501

Postgres Logs Explained: A Practical Guide for Production

Postgres 19 widens MultiXactOffset to 64 bits, eliminating the hidden 4 billion member limit that caused catastrophic outages for high-concurrency workloads.

Postgres 19 Feature Preview: 64-bit MultiXactOffset

A guide to MySQL schema migration best practice.

MySQL Schema Migration Best Practice

Postgres 19 introduces automatic sequence synchronization for logical replication, eliminating manual tracking and making major version upgrades and failover significantly easier.

Postgres 19 Feature Preview: Sequence Synchronization for Logical Replication

A guide to multi-environment deployments in databases.

Database Multi-Environment Deployments - The Challenges and Patterns

A guide to open source sensitive data discovery tools - from lightweight CLI scanners like PiiCatcher and Hawk-Eye to full data platforms like OpenMetadata.

Top Open Source Sensitive Data Discovery Tools in 2025

How to set up database audit logging for SOC 2, HIPAA, and ISO 27001 compliance across PostgreSQL, MySQL, SQL Server, and Oracle.

Database Audit Logging Best Practices for Compliance

A practical guide to HITRUST database compliance covering access control, audit logging, change management, and data protection.

Database Compliance for HITRUST: Controls, Risks, and Best Practices

Learn why requiring a primary key is important and how the "Require Primary Key" review rule protects your production database.

SQL Review Rule Explained - Require Primary Key

Learn why enforcing NOT VALID in CHECK constraints is important and how the "Enforce NOT VALID in CHECK" review rule protects your production database.

SQL Review Rule Explained - Enforce NOT VALID in CHECK

Postgres Audit Logging Guide

Learn why CASCADE operations in SQL can lead to catastrophic data loss and how the "Prohibit CASCADE" review rule protects your production database.

SQL Review Rule Explained - Prohibit CASCADE

A comprehensive guide on migrating from Supabase to AWS, covering database, auth, storage, functions, realtime, and networking.

How to Migrate from Supabase to AWS

Top open-source Postgres backup solutions for 2026.

What is Enterprise Database Management (EDM)?

What is Postgres Transaction ID (XID) Wraparound and how to monitor and prevent it.

Postgres Transaction ID (XID) Wraparound

A comprehensive guide on building a CI/CD pipeline for automated database schema migration, covering best practices, tools, and implementation strategies.

How to Build a CI/CD Pipeline for Database Schema Migration

A practical guide to shipping features efficiently using PostgreSQL, covering development workflows, best practices, and real-world examples

How I Ship Features with Postgres

A comprehensive overview of the essential practices and principles necessary for achieving LGPD (Brazilian General Personal Data Protection Act), compliance within database operations, and its difference with GDPR

Database Compliance for LGPD: Implications and Best Practices

Explain what is Postgres LATERAL JOIN and how to use it.

What is Postgres LATERAL JOIN?

Introduction to MySQL Online DDL and its three algorithms: INSTANT, INPLACE, and COPY

MySQL Online DDL: A Practical Guide

List of open source postgres connection poolers

Open Source Postgres Connection Pooler

A comprehensive guide to understanding the dilemma of singular vs. plural table naming in SQL databases.

SQL Table Naming Dilemma: Singular vs. Plural

Overview of PostgreSQL 18 features from a developer's perspective

What's New in PostgreSQL 18 - a Developer's Perspective

Explore Snowflake Dynamic Data Masking capabilities and compare with alternative data masking solutions

Snowflake Dynamic Data Masking (DDM) and Alternatives

Top open-source Postgres authentication solutions for 2025.

Postgres Case Sensitivity Explained

A comprehensive guide to understanding pg_database_owner in Postgres

What is pg_database_owner in Postgres

Which operation causes a Postgres table rewrite

Which Postgres Operation causes a table rewrite

An engineering perspective to evaluate Postgres row-level-security footguns

Common Postgres Row-Level-Security footguns

An engineering perspective to evaluate Postgres rollback strategies

Postgres Rollback Explained

Learn how Postgres locks affect schema migrations and which DDL operations conflict with DML to achieve zero-downtime deployments.

Postgres Schema Migration without Downtime Best Practice

A checklist of gh-ost limitations and potential gotchas

gh-ost Limitations You Need to Know Before Production

5 quick wins for application developers to improve Postgres reliability and make both their own and DBA/infrastructure teams' lives easier.

5 Postgres Production Tips for Application Developers

Learn how to use CREATE INDEX CONCURRENTLY in Postgres to build indexes without blocking writes. Pitfalls, safety checks, and performance tips.

How to Use Postgres CREATE INDEX CONCURRENTLY

An extensive comparison between Supabase and MongoDB on performance, usability, operability, ecosystem and more.

Supabase vs. MongoDB: a Complete Comparison in 2025

When evaluating database management tools, DataGrip and Bytebase represent two different philosophies: individual developer productivity versus team collaboration and governance.

Bytebase vs. DataGrip: a side-by-side comparison for database management

Supabase pricing starts free. We break down real costs for Pro ($25/mo) and Team ($599/mo) plans, explain overages, and compare each service head-to-head with AWS.

Supabase vs AWS: Feature and Pricing Comparison (2026)

Is Supabase free? Compare Supabase pricing vs AWS RDS and Aurora across free tier, Pro, and production plans. Includes Supabase free tier limits, storage costs, and compute pricing for 2026.

Supabase Pricing vs AWS RDS: Is Supabase Free? Full Cost Comparison (2026)

Learn how Bytebase enables organizations to implement comprehensive Database Security Lifecycle Management, unifying security and operations from development to production.

Database Security Lifecycle Management

Areas where MySQL shines and Postgres falls short.

Features I Wish Postgres Had but MySQL Already Has

Areas where PostgreSQL shines and MySQL falls short.

Features I Wish MySQL Had but Postgres Already Has

This guide focuses on HIPAA compliance at the database layer, providing healthcare organizations and database teams with practical guidance for implementing HIPAA Security Rule requirements.

HIPAA Data Security and Retention Requirements

Compare the online index creation difference between Postgres and MySQL

Postgres vs. MySQL: Online Index Creation

SOC 2 Data Security and Retention Requirements for Database Systems and How Bytebase Helps

SOC 2 Data Security and Retention Requirements

Compare the different indexing options between Postgres and MySQL

Postgres vs. MySQL: Indexing Options

Compare the JSON support difference between Postgres and MySQL

Postgres vs. MySQL: JSON Support

While PostgreSQL RLS is a powerful feature, it has inherent design limitations that hinder broader adoption. In this post, we’ll examine these limitations and explore alternatives.

PostgreSQL Row-level Security (RLS) Limitations and Alternatives

Evaluate several database schema diagram tools, and help you to choose the right one for 2025

Top 4 Free, Open Source Database Schema Diagram Tools to Visualize Database Easier in 2025

An overview of the most popular text-to-SQL AI tools in 2026, including DataGrip, TablePlus, SQL Chat, Vanna.ai, SQLAI.ai, Postgres.new, and DBHub MCP server. Compare features and capabilities to find the best SQL AI assistant for your workflow.

Top 5 Text-to-SQL Query Tools in 2026

Compare the DDL transaction difference between Postgres and MySQL

Postgres vs. MySQL: DDL Transaction Difference

Evaluate several TypeScript ORMs, and help you to choose the right one for 2025

Top TypeScript ORM 2025

Evaluate Prisma and TypeORM, and help you to choose the right TypeScript ORM for 2025

Prisma vs TypeORM: The Better TypeScript ORM in 2025

Overview of PostgreSQL 18 features with spicy comments from a DBA's perspective

What's New in PostgreSQL 18 - a DBA's Perspective

Explore alternatives to Amazon RDS, including 

RDS Alternatives in 2025

An extensive comparison between DynamoDB and Cassandra on performance, usability, operability, ecosystem and more.

DynamoDB vs. Cassandra: a Complete Comparison in 2025

An extensive comparison between DynamoDB and MongoDB on performance, usability, operability, ecosystem and more.

RDS vs. DynamoDB: a Complete Comparison in 2025

gh-ost and pt-online-schema-change are two popular tools for online schema migration in MySQL. This article compares the features and capabilities of the two tools.

gh-ost vs pt-online-schema-change in 2025

GitHub and Bitbucket are both tools for code collaboration. This article compares the features and pricing of GitHub and Bitbucket.

GitHub vs Bitbucket:a Complete Comparison in 2025

Drizzle ORM vs Prisma comparison: type safety, performance, bundle size, serverless support, migrations, and ecosystem. Find out which TypeScript ORM is right for your project in 2026.

Drizzle ORM vs Prisma: Which TypeScript ORM Should You Use in 2026?

An engineering perspective to evaluate Google AlloyDB and Cloud SQL, and help you to choose the right Google Cloud database for 2025

AlloyDB vs. Cloud SQL: engineering guide to choose the right Google Cloud database for 2025

Understanding DynamoDB Pricing (2025)

A simple comparison of AWS Aurora versus RDS pricing in 2025, helping you understand key differences and choose the right database service for your needs and budget.

AWS Aurora vs. RDS Pricing: A Detailed Comparison 2025

Infrastructure as Code security tools help organizations identify vulnerabilities and misconfigurations in their infrastructure definitions. This post explores the top open-source IaC security tools available in 2025.

Top Open Source Infrastructure as Code (IaC) Security Tools in 2025

Compare the price of the mainstream managed PostgreSQL hosting providers

PostgreSQL Hosting Options in 2025: Pricing Comparison

Complete guide to AWS Aurora pricing: instance types and costs, Aurora Serverless v2 pricing, I/O-Optimized vs Standard, reserved instance savings, and real-world cost examples. Learn how to optimize your Aurora costs.

AWS Aurora Pricing Explained: Instance Types, Serverless, and Cost Optimization (2026)

Database governance tools help organizations manage database changes, enforce policies, and maintain data quality. This post explores the top open-source database governance tools available in 2025.

Top Open Source Database Governance Tools in 2025

Workflow orchestration tools help coordinate tasks, handle errors, and monitor execution processes. In this post, we are taking a look at open source workflow orchestration options

Top Open Source Workflow Orchestration Tools in 2025

Understanding AWS RDS Pricing (2025)

Compare the price of the mainstream managed MySQL hosting providers

MySQL Hosting Options in 2025: Pricing Comparison

A comprehensive guide to the best open-source Kubernetes cluster management tools in 2025, including Argo CD, Karmada, Sveltos, and Plural.

Top 4 Open Source Kubernetes Cluster Management Tools in 2025

An extensive comparison between GitLab CI and GitHub Actions on features, performance, and more.

GitLab CI vs. GitHub Actions: a Complete Comparison in 2025

Review the state of the Golang ORM and query builder

Choose the Right Golang ORM or Query Builder in 2025

Overview of MySQL 9 features with spicy comments

What's New in MySQL 9 - a DBA's Perspective

An extensive comparison between Oracle and PostgreSQL on data model, query language, scalability, performance, and more.

Oracle vs. PostgreSQL: a Complete Comparison in 2025

An extensive comparison between MongoDB and MySQL on data model, query language, scalability, performance, and more.

MongoDB vs MySQL: a Complete Comparison in 2025

An extensive comparison between MongoDB and Redis on performance, usability, operability, ecosystem and more.

MongoDB vs Redis: a Complete Comparison in 2025

DynamoDB and PostgreSQL are both popular databases, but they are different. This post compares them based on their key differences, strengths, and ideal use cases.

DynamoDB vs PostgreSQL: A Concise Comparison


Database access control is the set of policies and mechanisms that determine who can connect to a database, what operations they can perform, and how long that access lasts. It covers both authentication (proving identity) and authorization (granting permissions) at the database engine level, independently of application-layer controls.

Get it wrong and you are one `DROP TABLE` away from a production incident, or one leaked credential away from a compliance violation. Most teams start with a shared admin account and a handful of application credentials. That works until the first [SOC 2 audit](/blog/soc2-data-security-and-retention-requirements/) asks *"who ran this query on March 3rd?"* and nobody can answer. This guide covers the principles, engine-specific mechanics, and common mistakes of database access control, along with practical ways to fix them.

## What a working access control system looks like

Even if your app restricts what users see in the UI, anyone with direct database credentials can bypass those restrictions entirely. A working access control system answers four questions:

1. **Who** is connecting? (A named individual, not a shared account.)
2. **What** can they do? (Read, write, alter schema, grant permissions to others.)
3. **Where** can they do it? (Which databases, schemas, tables, columns.)
4. **How long** does the access last? (Permanent, time-boxed, or on-demand.)

## Why access control matters for compliance

Every major compliance framework requires database-level access controls. The specific requirements overlap more than they differ:

| Framework | Access control requirement | Audit trail required? |
|-----------|---------------------------|----------------------|
| SOC 2 (CC6.1, CC6.3) | Least privilege, regular access reviews | Yes |
| [HIPAA](/blog/hipaa-data-security-and-retention-requirements/) (§164.312) | Unique user IDs, emergency access procedures | Yes |
| [GDPR](/blog/database-compliance-for-gdpr/) | Access limited to purpose of processing | Yes |
| PCI DSS (Req 7, 8) | Role-based access, no shared accounts | Yes |
| [SOX](/blog/database-change-management-sox-compliance/) | Separation of duties, change audit trails | Yes |
| ISO 27001 (A.9) | Formal access provisioning and de-provisioning | Yes |

The pattern is clear: restrict access to the minimum necessary, track every action, and review permissions regularly. Failing an audit because of overly broad database permissions is one of the most common compliance findings.

## Core principles

### Least privilege

Every user and application should have the minimum permissions required to do their job. A developer who needs to run `SELECT` queries against a staging database does not need `DROP` or `ALTER` privileges on production.

In practice, least privilege means:

- Application accounts get only `SELECT`, `INSERT`, `UPDATE`, `DELETE` on the tables they use
- Schema migration accounts are separate from application accounts
- Read-only replicas use credentials that cannot write
- Admin access is reserved for DBAs and granted per-session, not permanently

### Separation of duties

The person who writes a database change should not be the same person who approves and deploys it. This prevents both accidental mistakes and intentional abuse.

A typical separation looks like:

- **Developer** writes the migration SQL
- **DBA or tech lead** reviews the SQL for correctness and safety
- **Automated pipeline or separate role** executes the approved change
- **[Audit log](/blog/database-audit-logging/)** records who did what at each step

### Just-in-time access

Permanent standing access is the default in most organizations, and it is the wrong default. A developer who accessed the production database for a debugging session six months ago probably still has those credentials. If those credentials leak, the blast radius is the entire production dataset.

Just-in-time (JIT) access replaces permanent credentials with temporary, scoped grants:

1. User requests access to a specific database for a stated reason
2. An approver reviews and approves the request
3. The system grants access with a time limit (e.g., 2 hours)
4. Access is automatically revoked when the window closes

JIT access reduces standing privileges to near zero. Auditors prefer it because every access event has a documented reason and approval chain.

### Role-based access control (RBAC)

Managing permissions per user does not scale. RBAC groups permissions into roles and assigns roles to users. When someone joins a team, they inherit the team's role. When they leave, revoking the role removes all associated permissions in one step.

Common database roles:

| Role | Typical permissions |
|------|-------------------|
| `app_readonly` | `SELECT` on application tables |
| `app_readwrite` | `SELECT`, `INSERT`, `UPDATE`, `DELETE` on application tables |
| `schema_migrator` | `CREATE`, `ALTER`, `DROP` on schema objects |
| `dba_admin` | Full privileges, granted via JIT only |
| `analyst` | `SELECT` on reporting views and materialized views |

## How each database engine handles access control

Every major database has RBAC built in, but the syntax and defaults vary.

### PostgreSQL

PostgreSQL uses **roles** as both users and groups. A role can own objects, log in, and be a member of other roles.

```sql
-- Create a read-only role
CREATE ROLE app_readonly NOLOGIN;
GRANT CONNECT ON DATABASE myapp TO app_readonly;
GRANT USAGE ON SCHEMA public TO app_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO app_readonly;
-- Ensure future tables created by the migration role are also readable
ALTER DEFAULT PRIVILEGES FOR ROLE migrator IN SCHEMA public
  GRANT SELECT ON TABLES TO app_readonly;

-- Create a user that inherits the role
CREATE ROLE analyst LOGIN PASSWORD 'strong_password';
GRANT app_readonly TO analyst;
```

PostgreSQL's default is deny-all: a new role has no permissions on objects it does not own. The `ALTER DEFAULT PRIVILEGES` command is easy to forget but is needed to cover tables created in the future. Note that it only applies to objects created by the role that executes the statement. If a separate role (e.g., a migration role) creates tables, you must specify `FOR ROLE <owner>` or run the command as that role.

### MySQL

MySQL separates users (`CREATE USER`) from privileges (`GRANT`). There is no built-in role grouping in MySQL 5.7, but MySQL 8.0+ supports roles.

```sql
-- MySQL 8.0+ roles
CREATE ROLE 'app_readonly';
GRANT SELECT ON myapp.* TO 'app_readonly';

CREATE USER 'analyst'@'10.0.%' IDENTIFIED BY 'strong_password';
GRANT 'app_readonly' TO 'analyst'@'10.0.%';
SET DEFAULT ROLE 'app_readonly' TO 'analyst'@'10.0.%';
```

MySQL ties users to hostnames (`'user'@'host'`), which means the same person connecting from different networks can have different permissions. This is both a security feature and a source of confusion.

### SQL Server

SQL Server uses **logins** (server-level) and **users** (database-level), mapped together. It has built-in fixed server roles (`sysadmin`, `securityadmin`) and database roles (`db_datareader`, `db_datawriter`), plus support for custom roles.

```sql
-- Create a database role with read-only access
CREATE ROLE app_readonly;
GRANT SELECT ON SCHEMA::dbo TO app_readonly;

-- Create a login and map it to a database user
CREATE LOGIN analyst WITH PASSWORD = 'strong_password';
CREATE USER analyst FOR LOGIN analyst;
ALTER ROLE app_readonly ADD MEMBER analyst;
```

SQL Server's `DENY` takes precedence over `GRANT`, which allows for precise permission exclusions.

### Oracle

Oracle uses **profiles** and **roles** with fine-grained privileges. Oracle supports row-level security (Virtual Private Database) and data redaction natively.

```sql
-- Create a role
CREATE ROLE app_readonly;
GRANT SELECT ON schema.orders TO app_readonly;
GRANT SELECT ON schema.customers TO app_readonly;

-- Assign to a user
GRANT app_readonly TO analyst;
```

Oracle's `GRANT` syntax is similar to PostgreSQL, but Oracle also supports `GRANT ANY` privileges that operate across all schemas. These `ANY` privileges are powerful and should be avoided for non-DBA accounts.

## Common mistakes

**1. Shared service accounts.** Multiple developers sharing `admin@production` makes every query untraceable. When an auditor asks who ran a destructive query, the answer is "anyone on the team." Use individual accounts and map every connection to a real person.

**2. Copy-pasting permissions from another user.** When a new hire joins, the fastest path is to clone an existing user's grants. The problem is that the existing user has accumulated permissions over months. The new hire inherits permissions they do not need and the privilege creep compounds.

**3. Never revoking access.** People change teams, leave the company, or stop using certain databases. Without a regular access review cycle (monthly or quarterly), stale accounts accumulate. Automate de-provisioning through your identity provider where possible.

**4. Granting `ALL PRIVILEGES` because it is faster.** `GRANT ALL PRIVILEGES ON *.* TO 'app'@'%'` takes five seconds to type and months to clean up. Start with the minimum and add permissions as specific needs arise.

**5. No separation between application and human access.** Application service accounts and human developer accounts should be different. Applications need predictable, narrow permissions. Humans need broader permissions but only temporarily and with an audit trail.

**6. Ignoring schema-level isolation.** Databases that support schemas (PostgreSQL, SQL Server) give you a natural boundary for access control. Instead of granting access to individual tables, grant at the schema level and organize tables by access pattern.

## How Bytebase handles database access control

[Bytebase](https://www.bytebase.com) centralizes database access control across PostgreSQL, MySQL, SQL Server, Oracle, and other engines in a single interface. Instead of managing `GRANT` and `REVOKE` statements across multiple database clusters individually, teams manage permissions through Bytebase's two-level IAM system.

Key capabilities:

- **Two-level RBAC.** Bytebase has workspace-level roles (Admin, DBA, Member) and project-level roles (Owner, Developer, Releaser, SQL Editor User, Viewer). Each role maps to 100+ granular permissions. Organizations can also create custom roles with specific permission sets.
- **Conditional access with CEL expressions.** IAM bindings support [CEL](https://github.com/google/cel-spec) conditions, so you can scope access by database name, schema, or time window. For example, a binding can grant a developer query access to specific databases that expires on a set date.
- **Grant requests with expiration.** When a developer needs temporary access, they submit a grant request specifying the database, the role, and a duration. Once approved, the access expires automatically. This is the closest equivalent to just-in-time access.
- **Approval workflows.** Schema changes and data exports go through configurable approval chains with CEL-based matching rules. Approvers are resolved by role, so the request is automatically routed to the right DBA or project owner.
- **Dynamic data masking.** Masking rules use CEL conditions to match columns by environment, project, instance, database, table, column, or classification level. Masking exemption policies let specific users or groups bypass masking when needed, also with CEL conditions (including time-based expiration).
- **Query data policies.** Workspace and project-level policies control SQL Editor behavior: maximum result rows, whether data export is allowed, and whether copy-paste is enabled.
- **Audit logging.** Every query, schema change, and permission change is recorded with the real user identity, request metadata, and RPC latency. Logs are searchable with CEL filters and exportable. This [audit trail](/blog/database-audit-logging/) is what auditors need for SOC 2, HIPAA, and ISO 27001.
- **Groups and service accounts.** Users can be organized into groups and assigned roles as a group. Service accounts and workload identities (for CI/CD pipelines using OIDC) are first-class citizens in IAM bindings.

## FAQ

### What is the difference between authentication and authorization in databases?

Authentication verifies identity (who are you?). Authorization determines permissions (what can you do?). A database user must pass authentication first (usually with a password, certificate, or SSO token), then the database checks their authorization (granted roles and privileges) before allowing any operation.

### How often should database access be reviewed?

Quarterly reviews are the minimum for compliance. Monthly reviews are better for organizations with frequent team changes. Automated tools that flag unused accounts or permissions that haven't been exercised in 90 days reduce the manual work.

### Is row-level security considered access control?

Yes. Row-level security (RLS) restricts which rows a user can see within a table. PostgreSQL, SQL Server, and Oracle all support RLS natively. It is a form of authorization that operates at a finer grain than table-level `GRANT` and `REVOKE`.

### How does just-in-time access differ from VPN-based access control?

VPN controls which network can reach the database. JIT controls which person can access the database and for how long. They operate at different layers: a VPN alone does not satisfy least privilege because everyone on the VPN has the same network access. JIT adds identity-based, time-limited, and auditable access on top of network controls.



TRUNCATE and DELETE both remove rows from a table, but they work nothing alike under the hood. TRUNCATE drops all rows at once by deallocating the data pages. DELETE removes rows one at a time and logs each removal individually. This difference makes TRUNCATE faster on large tables, but it also means they behave differently with transactions, triggers, and foreign keys.

The bigger surprise: TRUNCATE is not even the same operation across databases. PostgreSQL treats it as a transactional command you can roll back. MySQL treats it as a DDL statement that commits immediately and cannot be undone. If you switch databases without knowing this, you will lose data.

## TRUNCATE vs DELETE at a glance

| | TRUNCATE | DELETE |
|---|---|---|
| Operation type | [DDL](/blog/what-is-ddl-and-dml-in-sql-database/) | [DML](/blog/what-is-ddl-and-dml-in-sql-database/) |
| Removes | All rows (no WHERE clause) | Selected rows (WHERE clause supported) |
| Speed on large tables | Fast (deallocates pages) | Slow (row-by-row logging) |
| Fires row-level triggers | No | Yes |
| Resets auto-increment / identity | Yes | No |
| Returns row count | No | Yes |
| Can be rolled back in PostgreSQL | Yes | Yes |
| Can be rolled back in MySQL | No (implicit commit) | Yes |
| Can be rolled back in SQL Server | Yes (within a transaction) | Yes |

The speed difference is not marginal. DELETE on a 47-million-row table scans every row and writes a WAL entry for each one. That can take hours. TRUNCATE on the same table finishes in under a second because it discards the data files without touching individual rows.

## TRUNCATE in PostgreSQL

PostgreSQL is the most flexible of the three. It wraps TRUNCATE inside transactions, just like any other command, so you can truncate a table and roll it back if something goes wrong.

```sql
BEGIN;
TRUNCATE employees;
-- Changed your mind?
ROLLBACK;
-- All rows are still there.
```

You also get control over auto-increment sequences:

```sql
-- Reset the sequence back to 1
TRUNCATE orders RESTART IDENTITY;

-- Keep the current sequence value
TRUNCATE orders CONTINUE IDENTITY;
```

Both the row removal and the sequence reset are transactional. Roll back, and the sequence returns to its previous value too. This is unusual. Even PostgreSQL's own `ALTER SEQUENCE RESTART` is not transactional outside of a TRUNCATE context.

For tables with foreign key references, PostgreSQL blocks TRUNCATE unless you add `CASCADE`:

```sql
-- This fails if other tables reference "orders"
TRUNCATE orders;

-- This truncates "orders" and any tables that reference it
TRUNCATE orders CASCADE;
```

Be careful with CASCADE. It silently empties every table linked by a foreign key chain, and on a schema with 30+ tables, that chain can reach tables you forgot were connected.

## TRUNCATE in MySQL

Different story. MySQL's TRUNCATE is a DDL statement that [causes an implicit commit](https://dev.mysql.com/doc/refman/8.0/en/implicit-commit.html), so it cannot be rolled back.

```sql
START TRANSACTION;
TRUNCATE employees;
-- The TRUNCATE already committed. ROLLBACK does nothing here.
ROLLBACK;
-- The table is empty.
```

This catches people who move from PostgreSQL to MySQL. They write TRUNCATE inside a transaction block expecting safety, and the data is gone the moment the statement runs. No warning, no error. The ROLLBACK succeeds silently and does nothing.

MySQL always resets AUTO_INCREMENT to 1 on TRUNCATE. No option to keep the current value, unlike PostgreSQL's `CONTINUE IDENTITY`.

Foreign keys are also handled differently. MySQL blocks TRUNCATE if the table is referenced by a foreign key from another table, even if the referencing table has zero rows. The workaround:

```sql
SET FOREIGN_KEY_CHECKS = 0;
TRUNCATE orders;
SET FOREIGN_KEY_CHECKS = 1;
```

Disabling foreign key checks is a blunt tool. If another session inserts rows referencing the truncated table while checks are off, you get orphaned records with no constraint violation. MySQL will not tell you about them.

## TRUNCATE in SQL Server

SQL Server sits between the two. It allows TRUNCATE inside explicit transactions (like PostgreSQL) but lacks the sequence control options.

```sql
BEGIN TRANSACTION;
TRUNCATE TABLE employees;
-- Safe to roll back
ROLLBACK;
```

The IDENTITY seed always resets. No equivalent to PostgreSQL's `CONTINUE IDENTITY`.

SQL Server is the strictest about foreign keys. It blocks TRUNCATE on any table referenced by a FOREIGN KEY constraint, even if `ON DELETE CASCADE` is defined. No CASCADE option for TRUNCATE, no `FOREIGN_KEY_CHECKS` toggle. Your only choices are DELETE or dropping the constraint entirely.

One edge case worth knowing: TRUNCATE also fails on tables that participate in indexed views or are published through transactional replication.

## When to use TRUNCATE vs DELETE

Use TRUNCATE for bulk cleanup: emptying staging tables between ETL loads, wiping test data, resetting a table after a failed migration. If the table has 10 million rows and you need all of them gone, TRUNCATE is the only practical option.

Use DELETE for everything else. You need a WHERE clause, you need triggers to fire, you need to know exactly how many rows were removed. DELETE is slower but it plays by the rules.

One recommendation: if you are writing application code that removes rows, always use DELETE. TRUNCATE belongs in migration scripts, maintenance jobs, and CI pipelines. Putting TRUNCATE in application logic is asking for trouble when someone adds a foreign key to that table six months later.

## TRUNCATE and foreign keys

All three databases block TRUNCATE when another table holds a foreign key reference. The workarounds differ, and none of them are safe to run blindly.

| Database | Workaround |
|---|---|
| PostgreSQL | `TRUNCATE table CASCADE` (truncates referencing tables too) |
| MySQL | `SET FOREIGN_KEY_CHECKS = 0` before TRUNCATE, re-enable after |
| SQL Server | Drop the foreign key constraint, TRUNCATE, recreate the constraint |

CASCADE can wipe tables you did not intend. Disabling foreign key checks opens a window for orphaned rows. Dropping and recreating constraints on a large schema is slow and error-prone.

If the table has foreign key dependencies, just use DELETE. Slower, but it respects constraints without workarounds and without the risk of silently destroying related data.

## How Bytebase prevents accidental TRUNCATE

Running TRUNCATE on a production table by accident takes seconds. Recovering from it takes hours if you have backups, and is impossible if you don't.

[Bytebase](/) provides [SQL review rules](https://www.bytebase.com/docs/sql-review/review-rules/) that flag or block TRUNCATE statements before they reach production. You can set policies like prohibiting TRUNCATE on production environments, requiring approval for DDL statements, or flagging CASCADE operations that touch multiple tables.

These rules run automatically when a developer submits a SQL change through Bytebase, catching dangerous statements during review rather than after execution. See [The SQL Review Tool for Developers](/blog/sql-review-tool-for-devs/) for how this fits into a team workflow.

## FAQ

**Is TRUNCATE faster than DELETE?**

Yes. TRUNCATE deallocates data pages without scanning or logging individual rows. On tables with millions of rows, TRUNCATE completes in under a second while DELETE can take minutes or hours.

**Does TRUNCATE reset AUTO_INCREMENT?**

Yes in all three databases. PostgreSQL gives you a choice with `RESTART IDENTITY` (reset) or `CONTINUE IDENTITY` (keep current value). MySQL and SQL Server always reset to the starting value.

**Can I TRUNCATE a table with foreign keys?**

Not directly. All three databases block TRUNCATE when another table references the target with a foreign key. PostgreSQL supports `CASCADE` to truncate referencing tables. MySQL requires disabling `FOREIGN_KEY_CHECKS`. SQL Server requires dropping the constraint first.

**Is TRUNCATE a DDL or DML statement?**

TRUNCATE is classified as [DDL (Data Definition Language)](/blog/what-is-ddl-and-dml-in-sql-database/). DELETE is DML. This classification explains why MySQL's TRUNCATE triggers an implicit commit: MySQL auto-commits all DDL statements. PostgreSQL and SQL Server handle it differently by allowing DDL inside transactions. For more on how [PostgreSQL and MySQL handle DDL transactions differently](/blog/postgres-vs-mysql-ddl-transaction/), see our detailed comparison.



Database design patterns are reusable structural approaches to organizing tables, relationships, and indexes in a relational database. Picking the wrong pattern early on is expensive. The pattern you choose defines your query performance ceiling, your data integrity guarantees, and how painful your next schema migration will be.

This guide covers six patterns that show up in most production systems, the trade-offs behind each, and the anti-patterns that cause real-world outages.

## What are database design patterns?

A database design pattern is a repeatable solution to a common data modeling problem. It is a structural decision about how tables relate to each other, how data is split or combined, and where you put the boundaries between entities. Some patterns optimize for write safety (normalization), others for read speed (star schema), others for flexibility (EAV, JSONB columns), and others for organizational isolation (multi-tenancy). Most production databases use several patterns together.

## Normalization (1NF through 3NF)

Normalization removes redundant data by splitting it across related tables. The goal is to make sure each fact is stored exactly once, so updates only happen in one place.

**First Normal Form (1NF):** Every column holds a single value. No comma-separated lists, no arrays stuffed into a VARCHAR. Each row is uniquely identifiable by a [primary key](/blog/primary-key-vs-foreign-key/).

**Second Normal Form (2NF):** Every non-key column depends on the entire primary key, not just part of it. This matters when you have composite keys. If an `order_items` table is keyed on `(order_id, product_id)`, the `product_name` depends only on `product_id` and should live in a separate `products` table.

**Third Normal Form (3NF):** Non-key columns depend only on the primary key, not on other non-key columns. If a `customers` table has `city` and `state`, and `city` determines `state`, then `state` should move to a `cities` table. This eliminates transitive dependencies.

### When to denormalize

3NF is the default target for transactional systems. But read-heavy workloads (dashboards, reports, search) often need denormalized data to avoid expensive multi-table joins. Denormalization means deliberately adding redundancy, like storing `total_orders_count` directly on a customer row instead of computing `COUNT(*)` from the orders table on every request.

The rule: start normalized, denormalize when you have measured evidence that a specific query is too slow.

## Star schema and snowflake schema

These patterns are for analytical workloads, not transactional ones.

**Star schema** puts a central fact table (containing measures like revenue, quantity, or duration) surrounded by denormalized dimension tables (date, product, customer, region). Each query is one join from fact to dimension. It is simple and fast.

**Snowflake schema** normalizes the dimension tables into sub-dimensions. A `location` dimension splits into `city → state → country` tables. This saves storage and improves data integrity at the cost of more joins.

| | Star schema | Snowflake schema |
|---|:-:|:-:|
| **Dimension tables** | Denormalized | Normalized into sub-tables |
| **Query joins** | Fewer | More |
| **Storage** | Higher (redundant data) | Lower |
| **Query speed** | Faster | Slower |
| **Best for** | Dashboards, ad-hoc BI | Complex hierarchies, storage-sensitive environments |

Modern columnar warehouses (Snowflake, BigQuery, Redshift) have optimized away much of the performance penalty of snowflake schemas, so the choice is less about speed and more about how your team thinks about the data. Star schema remains the default for most [analytics use cases](/blog/top-database-schema-diagram-tools/) because it is easier to understand and query.

## Entity-Attribute-Value (EAV)

EAV stores data in three columns: `entity_id`, `attribute_name`, and `value`. Instead of a wide table with one column per attribute, each attribute becomes a row.

```sql
-- EAV table
CREATE TABLE product_attributes (
    entity_id   INT REFERENCES products(id),
    attribute   VARCHAR(100),
    value       VARCHAR(255)
);

-- A T-shirt has size and color; a laptop has cpu and ram_gb.
-- Both go in the same table.
INSERT INTO product_attributes VALUES (1, 'size', 'XL');
INSERT INTO product_attributes VALUES (1, 'color', 'blue');
INSERT INTO product_attributes VALUES (2, 'cpu', 'M3 Pro');
INSERT INTO product_attributes VALUES (2, 'ram_gb', '36');
```

**When it looks attractive:** Product catalogs with hundreds of optional attributes. Clinical records with thousands of possible fields per patient.

**Why it usually fails:** Every query that retrieves multiple attributes requires self-joins or pivot operations. Filtering is slow because `value` is always VARCHAR (no type checking, no numeric indexing). Magento 1.x used EAV for product data and was notorious for poor query performance at scale. PostgreSQL benchmarks show that JSONB is over 50,000x faster than EAV for unindexed queries, while producing a database 3x smaller.

**The modern alternative:** Use typed columns for core fields and a JSONB column for the variable remainder:

```sql
CREATE TABLE products (
    id          SERIAL PRIMARY KEY,
    name        VARCHAR(200) NOT NULL,
    price       DECIMAL(10,2) NOT NULL,
    category_id INT REFERENCES categories(id),
    attributes  JSONB DEFAULT '{}'
);
```

Rule of thumb: if you write `WHERE attributes->>'status' = 'active'` in most queries, `status` should be a proper column, not buried in JSON.

## Polymorphic associations

A polymorphic association uses a single [foreign key](/blog/primary-key-vs-foreign-key/) column plus a "type" column to reference rows in multiple different tables.

```sql
CREATE TABLE comments (
    id              SERIAL PRIMARY KEY,
    body            TEXT,
    commentable_id  INT,          -- could point to posts, photos, or videos
    commentable_type VARCHAR(50)  -- 'Post', 'Photo', or 'Video'
);
```

This pattern is common in Rails and Django ORMs. The problem: the database cannot enforce a foreign key constraint because `commentable_id` points to different tables depending on `commentable_type`. That means no CASCADE deletes, no referential integrity checks, and orphaned records that accumulate silently.

GitLab's engineering documentation explicitly recommends against polymorphic associations. The alternative: separate association tables per type.

```sql
CREATE TABLE post_comments (
    id      SERIAL PRIMARY KEY,
    body    TEXT,
    post_id INT REFERENCES posts(id) ON DELETE CASCADE
);

CREATE TABLE photo_comments (
    id       SERIAL PRIMARY KEY,
    body     TEXT,
    photo_id INT REFERENCES photos(id) ON DELETE CASCADE
);
```

More tables, but the database enforces every relationship. This is almost always the right trade-off for systems that need long-term data integrity.

## Multi-tenant patterns

Multi-tenancy decides how you isolate customer data when multiple organizations share the same application. There are three standard approaches, each with a different cost-isolation trade-off.

**Shared schema (pool model):** All tenants share the same tables. A `tenant_id` column on every table separates the data. Cheapest and simplest, but a missing `WHERE tenant_id = ?` filter can leak data across tenants.

**Schema-per-tenant:** Each tenant gets a separate schema within the same database instance. Supported in PostgreSQL and SQL Server, but not in MySQL. Bytebase's analysis [found that it introduces complexity comparable to database-per-tenant](/blog/multi-tenant-database-architecture-patterns-explained/) without proportional isolation benefits.

**Database-per-tenant (silo model):** Each tenant gets a fully separate database. Maximum isolation, but the highest operational cost. Managing schema migrations across hundreds of databases requires [dedicated tooling](/blog/how-to-handle-database-schema-change/).

| | Shared schema | Schema-per-tenant | Database-per-tenant |
|---|:-:|:-:|:-:|
| **Cost** | Lowest | Medium | Highest |
| **Data isolation** | Weakest | Medium | Strongest |
| **Per-tenant customization** | None | Some | Full |
| **Migration complexity** | One migration | Per-schema | Per-database |
| **Best for** | Startups, MVPs | Mid-tier SaaS | Enterprise, regulated industries |

Start with shared schema unless you have a compliance requirement (HIPAA, GDPR data residency) that demands physical isolation. PostgreSQL's [row-level security](/blog/postgres-row-level-security-limitations-and-alternatives/) can add a database-enforced isolation layer on top of application-level `tenant_id` filtering.

## Anti-patterns to avoid

These are the design decisions that cause production incidents.

**The God Table.** One table stores everything: users, orders, products, logs. It starts with 50 columns and grows to 200. Splitting into focused tables typically reduces query times by 80% or more.

**Missing primary keys.** Always use a [surrogate primary key](/blog/choose-primary-key-uuid-or-auto-increment/) (auto-increment integer or UUID). Natural keys like name + date of birth lead to collisions and mixed-up records.

**Over-normalization.** Splitting data across too many tables where simple queries require 10+ joins. A fintech startup decomposed currency codes, transaction types, and timestamp components into separate lookup tables, and the system collapsed under peak load.

**Storing money as FLOAT.** Floating-point arithmetic causes rounding errors. `0.1 + 0.2 = 0.30000000000000004` in most languages. Use DECIMAL(10,2) for monetary values.

**No indexes on filtered columns.** Index the columns that appear in your WHERE clauses and JOIN conditions, and use EXPLAIN to validate. Too many indexes slow writes; too few cause full table scans.

**Wrong data types.** Dates stored as VARCHAR prevent range queries. Enums stored as freeform strings allow typos. Use DATE/TIMESTAMP for times, DECIMAL for money, and ENUM or lookup tables for fixed value sets.

Getting the pattern right at the [schema design](/blog/top-database-schema-design-best-practices/) stage is cheaper than fixing it in production.

## How Bytebase helps enforce design patterns

[Bytebase](/) is a database DevSecOps platform that catches pattern violations before they reach production. Its [SQL review](/blog/what-is-sql-review/) policy can enforce rules like:

- [Every table must have a primary key](/blog/sql-review-rule-explained-require-primary-key/)
- Column naming must follow conventions (e.g., `_id` suffix for foreign keys, `_at` suffix for timestamps)
- [CASCADE operations must be explicitly approved](/blog/sql-review-rule-explained-prohibit-cascade/)
- Specific column types are required for specific data (TIMESTAMP for dates, DECIMAL for currency)

These rules run automatically on every [schema change](/blog/what-is-database-schema/) before it is applied, which means pattern violations get caught in review, not in a 3 AM incident.

## Further readings

- [Top 10 Database Schema Design Best Practices](/blog/top-database-schema-design-best-practices/)
- [What is a Database Schema?](/blog/what-is-database-schema/)
- [Multi-Tenant Database Architecture Patterns Explained](/blog/multi-tenant-database-architecture-patterns-explained/)
- [Primary Key vs Foreign Key](/blog/primary-key-vs-foreign-key/)
- [DDL vs DML in SQL](/blog/what-is-ddl-and-dml-in-sql-database/)
- [How to Handle Database Migration / Schema Change](/blog/how-to-handle-database-schema-change/)



pgvector is a PostgreSQL extension that lets you store vectors in a table column and search them by similarity. It reached version 0.8.2 in late 2025 and is now included by default on most hosted PostgreSQL services (AWS RDS, Google Cloud SQL, Supabase, Neon). If you already run PostgreSQL, you can add vector search without a separate database.

Vectors are arrays of numbers that represent meaning. A sentence about "database migrations" and a sentence about "schema changes" would have vectors that sit close to each other, even though they share no keywords. This closeness is what makes vector search useful for AI applications: it finds semantically related content rather than exact word matches.

## What pgvector stores

An embedding model converts text into a list of numbers. Send "I love coffee" to the model and it returns 1,536 numbers. Send "I enjoy espresso" and it returns a nearly identical list — even though the words are completely different. Send "database migration" and the numbers look nothing like either of those. The model learned these relationships from patterns in text; you don't define them yourself.

pgvector adds a column type to PostgreSQL that stores these lists. You set the dimension count when you create the column (1,536 for OpenAI's `text-embedding-3-small`) and it stays fixed. When you search, pgvector finds the rows whose numbers are closest to your query — which means closest in meaning, not in wording.

## Installing pgvector

On a self-hosted PostgreSQL server:

```bash
# Ubuntu/Debian
sudo apt install postgresql-16-pgvector

# macOS with Homebrew
brew install pgvector
```

Then enable it inside the database:

```sql
CREATE EXTENSION vector;
```

On hosted services (RDS, Google Cloud SQL, Supabase, Neon), the package is already installed. `CREATE EXTENSION vector;` is all you need.

## Storing and querying vectors

You add a `vector` column to any table and store embeddings like any other value:

```sql
CREATE TABLE documents (
  id        SERIAL PRIMARY KEY,
  content   TEXT,
  embedding vector(1536)
);
```

In practice, you generate embeddings in application code by sending text to an embedding model (OpenAI, Cohere, a local model), then insert the returned array. To search, you pass a query embedding and order by distance:

```sql
-- Find the 5 documents most similar to a query
SELECT content, embedding <=> $1 AS distance
FROM documents
ORDER BY embedding <=> $1
LIMIT 5;
```

The `<=>` operator computes cosine distance, the most common choice for text. pgvector also supports L2 distance (`<->`) and inner product (`<#>`). The key advantage over dedicated vector databases: you can combine vector search with any SQL filter or join in the same query.

## Indexing for performance

Without an index, every similarity query scans every row. That works fine up to ~100,000 rows but slows down beyond that. Add an HNSW index to switch to approximate nearest-neighbor search, which is much faster at the cost of very slightly less precision:

```sql
CREATE INDEX ON documents USING hnsw (embedding vector_cosine_ops);
```

HNSW can be created on an empty table and handles new inserts without rebuilding. Use `CREATE INDEX CONCURRENTLY` on large tables to avoid locking. pgvector also has an IVFFlat index type for lower memory usage, but HNSW is the better default for most cases.

## pgvector vs. a dedicated vector database

The main alternative to pgvector is a purpose-built vector database: Pinecone, Weaviate, Qdrant, or Milvus. The right choice depends on scale and operational complexity.

| Factor | pgvector | Dedicated vector DB |
|--------|----------|---------------------|
| Setup | `CREATE EXTENSION` | Separate service to run |
| SQL joins and filters | Yes, natively | Metadata filtering only |
| ACID transactions | Yes | Varies |
| Comfortable scale | Up to ~10M rows | Hundreds of millions |
| Operational overhead | Existing PostgreSQL infra | New service to manage |
| Managed options | RDS, Supabase, Neon | Pinecone, Weaviate Cloud |

For most teams building a first RAG pipeline or adding semantic search to an existing product, pgvector is the right starting point. You get vector search without adding infrastructure, and your vectors live next to your relational data where you can query them together.

Purpose-built databases make sense at very large scale (50M+ vectors), when you need extremely low query latency, or when you want built-in hybrid search. [PostgreSQL vs MongoDB](/blog/postgres-vs-mongodb/) covers a related trade-off: MongoDB Atlas has its own vector search, and if your data is already there, it may be the simpler path.

## pgvector and schema migrations

Adding pgvector to a production database is a schema change like any other: you enable an extension, add columns, and build indexes. A few things worth knowing:

- HNSW index builds are CPU-intensive. Use `CREATE INDEX CONCURRENTLY` on production tables.
- Switching embedding models means changing the dimension count, which requires dropping the old column and backfilling all embeddings. Plan this as a multi-step migration.

pgvector follows the same lifecycle as any other PostgreSQL extension: enable it in staging first, verify the version matches production, then roll it out. [What is database migration?](/blog/what-is-database-migration/) covers safe sequencing. pgvector is also consistently listed among the [top PostgreSQL extensions](/blog/top-postgres-extension/) in active use.

[Bytebase](https://www.bytebase.com) handles PostgreSQL schema migrations with a review step before SQL runs in production, keeping a full history of every change — including extension additions and index builds. For teams managing pgvector alongside other [PostgreSQL schema changes](/blog/postgres-schema-migration-without-downtime/), that review step catches problems before they reach production.

## FAQ

**Does pgvector work with all PostgreSQL hosting providers?**
Most major providers include it as of 2024: AWS RDS (PostgreSQL 15.2+), Google Cloud SQL, Azure Database for PostgreSQL, Supabase, Neon, and Render.

**How many vectors can pgvector handle?**
Most teams run comfortably up to 5-10 million vectors on a well-sized PostgreSQL instance. Approximate indexes (HNSW, IVFFlat) help the most past 100,000 rows. Beyond ~50M vectors, a dedicated vector database is worth evaluating.

**Is pgvector production-ready?**
Yes. pgvector 0.7.0 (March 2024) added HNSW indexing, which was the main gap for production workloads. Version 0.8.2 is the current stable release. It runs in production at Supabase, Neon, and many teams building RAG applications.



An upsert is a single database operation that inserts a new row or updates an existing one, depending on whether a conflict is found on a primary key or unique index. The term blends "update" and "insert." Most SQL databases support the pattern natively but with different syntax: MySQL uses `INSERT ... ON DUPLICATE KEY UPDATE`, PostgreSQL uses `INSERT ... ON CONFLICT`, and SQL Server uses `MERGE`.

Each implementation has edge cases that behave differently when many users write at the same time or on tables with multiple unique indexes. This guide covers the syntax for each database, the pitfalls worth knowing before you ship, and how upserts interact with migrations.

## What is upsert and when to use it

An upsert is useful whenever you need to write data without first checking whether a row already exists. Common scenarios:

- **Syncing external data**: pull records from an API and write them to a local table; update the row if it's already there, insert if not
- **Safe retries**: if a write fails and you retry it, upsert produces the same result whether it runs once or ten times
- **Counters**: increment a value if the row exists, or start it from scratch if not
- **Seed data in migrations**: write default rows that should always exist, without failing if they're already there

Without native upsert support, the usual pattern is SELECT-then-INSERT/UPDATE: two separate queries with a gap between them where two users can race to insert the same row. Upsert collapses this into one step.

## MySQL: INSERT ON DUPLICATE KEY UPDATE

MySQL's upsert syntax:

```sql
INSERT INTO table (col1, col2, ...)
VALUES (val1, val2, ...)
ON DUPLICATE KEY UPDATE col2 = VALUES(col2), ...;
```

When the row you're inserting would conflict with an existing primary key or unique index, MySQL runs the `UPDATE` clause instead of failing. The `VALUES()` function (MySQL 5.x) or column aliases (MySQL 8.0.19+) let you reference the new values inside the `UPDATE` clause:

```sql
-- MySQL 8.0.19+ (preferred)
INSERT INTO page_views (page_id, view_count)
VALUES (42, 1) AS new_vals
ON DUPLICATE KEY UPDATE view_count = view_count + new_vals.view_count;

-- Older syntax using VALUES() function
INSERT INTO page_views (page_id, view_count)
VALUES (42, 1)
ON DUPLICATE KEY UPDATE view_count = view_count + VALUES(view_count);
```

**Affected rows behavior**

MySQL's affected-rows count is non-obvious:

| Result | Affected rows |
|--------|--------------|
| Row inserted | 1 |
| Existing row updated | 2 |
| Row matched, no columns changed | 0 |

This matters if your code checks the affected-row count to decide what happened. Most ORMs hide this, but raw database clients expose the raw number.

**The multiple unique index caveat**

If a table has more than one unique or primary key index and the row you're inserting matches more than one of them, MySQL only runs the update for whichever index it finds first. MySQL's own documentation warns against using `ON DUPLICATE KEY UPDATE` on tables like this. The result depends on internal index ordering and isn't predictable.

For tables with a single primary key (the most common case), the behavior is straightforward. One thing to know: for [AUTO_INCREMENT primary keys](/reference/mysql/how-to/how-to-use-auto-increment-mysql/), the counter still ticks up even when a conflict happens and no row is inserted, which can leave gaps in your IDs.

**REPLACE INTO: skip this**

MySQL also has `REPLACE INTO`, which handles conflicts by deleting the old row and inserting a fresh one. This resets the primary key on auto-increment tables, fires DELETE + INSERT triggers instead of UPDATE triggers, and can break foreign key relationships that point at the deleted row. Stick with `ON DUPLICATE KEY UPDATE` instead.

## PostgreSQL: INSERT ... ON CONFLICT

PostgreSQL added `INSERT ... ON CONFLICT` in version 9.5. The syntax:

```sql
INSERT INTO table (col1, col2, ...)
VALUES (val1, val2, ...)
ON CONFLICT (conflict_column)
DO UPDATE SET col2 = EXCLUDED.col2, ...;
```

`EXCLUDED` is a special name PostgreSQL gives to the row you tried to insert. You can use it anywhere in the `SET` clause, which is cleaner than MySQL's `VALUES()` approach:

```sql
INSERT INTO page_views (page_id, view_count, last_seen)
VALUES (42, 1, NOW())
ON CONFLICT (page_id)
DO UPDATE SET
    view_count = page_views.view_count + EXCLUDED.view_count,
    last_seen = EXCLUDED.last_seen;
```

**DO NOTHING**

When you want to silently skip conflicts rather than update:

```sql
INSERT INTO users (email, name)
VALUES ('alice@example.com', 'Alice')
ON CONFLICT (email) DO NOTHING;
```

`DO NOTHING` is useful for seed data you're safe to re-run, or any pipeline where a duplicate just means the work was already done.

**Conflict target options**

PostgreSQL requires a conflict target when using `DO UPDATE`:

```sql
-- By column (most common; infers the unique index)
ON CONFLICT (email) DO UPDATE SET name = EXCLUDED.name

-- By named constraint
ON CONFLICT ON CONSTRAINT users_email_key DO NOTHING

-- By partial unique index
ON CONFLICT (user_id) WHERE is_active = true DO UPDATE SET ...
```

Using column names is usually safer than hard-coding a constraint name: `ON CONFLICT (email)` keeps working if you drop and recreate the unique constraint (or PostgreSQL rebuilds the underlying index), while `ON CONFLICT ON CONSTRAINT users_email_key` breaks if that specific constraint name no longer exists.

**Safe under concurrent writes**

`INSERT ... ON CONFLICT` is safe when multiple users or processes write to the same table at the same time. PostgreSQL guarantees that exactly one insert or update fires per row; two sessions can't both "win" on the same row. This is safer than the SELECT-then-INSERT pattern, where a second user can slip in between your SELECT and your INSERT.

## SQL Server and other databases

**SQL Server: MERGE**

SQL Server uses `MERGE`, which is also the SQL standard syntax (SQL:2003):

```sql
MERGE INTO target_table AS target
USING (VALUES (42, 1)) AS source (page_id, view_count)
ON target.page_id = source.page_id
WHEN MATCHED THEN
    UPDATE SET target.view_count = target.view_count + source.view_count
WHEN NOT MATCHED THEN
    INSERT (page_id, view_count) VALUES (source.page_id, source.view_count);
```

`MERGE` requires a semicolon terminator; omitting it raises Error 10713.

`MERGE` is more verbose than MySQL or PostgreSQL upsert, but also more general. You can handle MATCHED, NOT MATCHED BY TARGET, and NOT MATCHED BY SOURCE in one statement, which makes it suitable for full table synchronization. [MySQL vs SQL Server](/blog/mysql-vs-sqlserver/) covers more syntax differences between the two.

**SQLite**

SQLite uses `INSERT OR REPLACE` (same delete-then-insert problem as MySQL's `REPLACE INTO`) or the cleaner `INSERT ... ON CONFLICT` syntax added in version 3.24.0 (released June 2018), which closely mirrors PostgreSQL. If you are on an older SQLite version, upgrade before relying on `ON CONFLICT DO UPDATE`.

```sql
INSERT INTO page_views (page_id, view_count)
VALUES (42, 1)
ON CONFLICT(page_id) DO UPDATE SET view_count = view_count + excluded.view_count;
```

Note: SQLite spells `excluded` in lowercase; PostgreSQL accepts both cases.

**Oracle**

Oracle uses `MERGE` with syntax similar to SQL Server. There is no `INSERT ... ON CONFLICT` shorthand.

## Performance and locking considerations

Upserts save a round trip compared to SELECT-then-INSERT/UPDATE, but they do come with some locking overhead.

**MySQL locking**

`ON DUPLICATE KEY UPDATE` locks the conflicting row even when the update doesn't change any values. On tables with heavy write traffic and frequent conflicts, this can increase wait times. For workloads where most writes are new inserts (conflicts are rare), it can be faster to catch the duplicate-key error in your application code and retry as an UPDATE. Only worth doing if you handle the exception carefully.

**PostgreSQL**

`INSERT ... ON CONFLICT` locks the conflicting row only for the duration of that statement, then releases it. Multiple users can safely upsert to the same table at the same time without stepping on each other.

**Deadlocks in batch upserts**

When two users upsert batches of rows at the same time, they can get stuck waiting for each other if their batches overlap in opposite orders. For example, user A is holding a lock on row 1 and waiting for row 2, while user B is holding row 2 and waiting for row 1. The fix is simple: sort your rows by primary key before batching so every session processes them in the same order:

```sql
-- Sort by primary key before batching
INSERT INTO page_views (page_id, view_count)
VALUES (1, 5), (2, 3), (7, 1)
ON CONFLICT (page_id)
DO UPDATE SET view_count = page_views.view_count + EXCLUDED.view_count;
```

**Checking what happened (PostgreSQL)**

PostgreSQL's `RETURNING` clause lets you see whether the row was inserted or updated:

```sql
INSERT INTO users (email, name)
VALUES ('alice@example.com', 'Alice')
ON CONFLICT (email) DO UPDATE SET name = EXCLUDED.name
RETURNING xmax;
-- xmax = 0 → row was inserted; non-zero → row was updated
```

## Upsert in application code and migrations

**ORM support**

Most ORMs support upsert natively, but the method name varies:

| ORM | Method |
|-----|--------|
| Prisma | `upsert()` |
| Sequelize | `upsert()` |
| SQLAlchemy | `insert().on_conflict_do_update()` |
| Knex.js | `onConflict().merge()` |
| TypeORM | `save()` with `upsert: true` |

**Upserts in migration scripts**

Upsert-based seed data is safe to run more than once. Running the migration twice produces the same result. For reference tables (countries, currencies, status codes, permission names), this is much safer than a plain `INSERT`, which would fail if the rows are already there:

```sql
-- Safe to run multiple times
INSERT INTO currencies (code, name)
VALUES ('USD', 'US Dollar'), ('EUR', 'Euro')
ON CONFLICT (code) DO NOTHING;
```

One thing to watch for: if you add a `UNIQUE` constraint to a column as part of a migration, any duplicate values already in that column will cause the `ALTER TABLE` to fail before your upsert even runs. Clean up existing duplicates first. [What is Database Schema Migration?](/blog/what-is-database-migration/) covers safe migration sequencing in more detail.

Which conflicts an upsert detects depends entirely on which primary keys and unique indexes exist on the table. [Primary key vs foreign key](/blog/primary-key-vs-foreign-key/) explains the difference if you're working out why a particular upsert is or isn't triggering the update path.

## Bytebase and safe upsert migrations

Upsert patterns interact with schema changes in ways that aren't always obvious. Adding or removing a unique index changes which conflicts the upsert detects. Renaming a constraint in PostgreSQL breaks any `ON CONFLICT ON CONSTRAINT` references in your application code. Changing a column's data type can silently affect whether two rows are considered equal during the conflict check.

[Bytebase](https://www.bytebase.com) reviews schema migrations before they reach production. Its SQL review engine enforces rules like requiring indexes on columns used in WHERE clauses, blocking `DROP INDEX` without an explicit override, and flagging tables that lack a primary key — the same constraints that upsert logic depends on. For teams running [PostgreSQL and MySQL side by side](/blog/postgres-vs-mysql/), Bytebase runs the same review workflow against both databases regardless of which upsert dialect each one uses.

## FAQ

**What is the difference between upsert and MERGE?**
`MERGE` is the SQL standard way to do an upsert, used by SQL Server and Oracle. MySQL and PostgreSQL have their own shorter syntax that covers the insert-or-update case. `MERGE` can also handle DELETE in the same statement, which makes it useful for syncing a whole table, not just individual rows.

**Can I use ON CONFLICT with a two-column unique index in PostgreSQL?**
Yes. List both columns: `ON CONFLICT (col1, col2) DO UPDATE SET ...`. PostgreSQL will find the unique index that covers exactly those columns. If no such index exists, you'll get an error at runtime.

**Why does MySQL ON DUPLICATE KEY UPDATE return 2 affected rows on an update?**
MySQL's convention: 1 = row was inserted, 2 = existing row was updated, 0 = row matched but nothing changed. It's intentional and documented. Most ORMs hide this, but raw database clients return the raw number.

**Is REPLACE INTO the same as upsert?**
No. `REPLACE INTO` deletes the old row and inserts a brand new one. This resets the primary key on auto-increment tables, fires DELETE triggers instead of UPDATE triggers, and can break foreign keys that point at the deleted row. Use `INSERT ... ON DUPLICATE KEY UPDATE` instead.

**Does PostgreSQL ON CONFLICT work with partial indexes?**
Yes. If your unique index was created with a `WHERE` clause, include the same condition in the conflict target: `ON CONFLICT (col) WHERE is_active = true DO UPDATE SET ...`. PostgreSQL only uses the partial index when the row being inserted matches that condition.


The
Bytebase Blog

Explore the standard for database development

Solutions & Platform

Comparisons

Legal

Resources

Company