Skip to main content
GitLab
Chewy.com
Miro
OnGres
Qiwi
Nutanix

Instantly clone your production database and...

Eliminate downtime caused by poorly tested database changes

Eliminate downtime caused by
poorly tested database changes

Optimize SQL queries

Test your SQL optimizations on a
realistic, risk-free database clone

Easily access fresh data for development and testing

Easily access fresh data
for development and testing

Mask personal and sensitive data

Maintain security and compliance by
masking sensitive data

Use-Case2

Automatically verify
your database migrations

Verify database changes in CI

Integrate database migration testing into your CI/CD pipeline and verify that any DDL or DML change will run correctly on production.

Understand how your database migrations will perform before you deploy.

Eliminate database-related downtime risk.

Learn more

Use-Case2

Automatically verify
your database migrations

Verify database changes in CI

Integrate database migration testing into your CI/CD pipeline and verify that any DDL or DML change will run correctly on production.

Understand how your database migrations will perform before you deploy.

Eliminate database-related downtime risk.

Learn more

Optimize SQL on
production database clones

Optimize SQL on
production database clones

Optimize SQL on an instantly provisioned, independent, production clone and stop experimenting on live data.

Joe Bot, our virtual DBA, runs on top of Database Lab to help you find and fix bottlenecks.

Iterate as many times as you want to achieve the best results.

Learn more

Use-Case3
Use-Case1

Run staging and test apps
with full data

Run staging and test apps
with full data

Understand exactly how your application will behave on production.

Give each developer their own full-size database without the hassle and cost.

Simplify the setup and onboarding of new teammates.

Learn more

The latest from our blog

DLE 2.5: Better data extraction for logical mode and configuration improvements

DLE 2.5: Better data extraction for logical mode and configuration improvements

Now it is possible to dump/restore multiple databases at the same time and use different pg_dump formats and compression formats of plain-text dump. DLE and related products configuration structure were significantly reworked and require manual action to migrate to the new version.
What is a slow SQL query?

What is a slow SQL query?

Is 200 ms slow for an SQL query? What about 20 ms? When do we need to optimize?
PostgreSQL Subtransactions Considered Harmful

PostgreSQL Subtransactions Considered Harmful

PostgreSQL subtransactions (nested transactions) may cause multiple performance and scalability issues: higher rates of XID growth and higher risks of transaction ID wraparound, performance degradation when more than PGPROC_MAX_CACHED_SUBXIDS (64) are used in a session, drastic performance slowdowns when subtransactions are combined with SELECT .. FOR UPDATE, and finally, brief downtime on standbys when subtranasctions used on the primary in paralell with long-running transactions or just slow statements. Subtransactions can be created using SAVEPOINT in regular SQL or using EXCEPTION WHEN blocks in PL/pgSQL.