Skip to main content

DLE 3.2: config and logs in UI, Postgres 15, AWS Marketplace version is GA

· 4 min read

Database Lab Engine 3.2 by config and logs in UI, Postgres 15, AWS Marketplace version is GA

The team is happy to announce the release of version 3.2 of Database Lab Engine (DLE), an open-source tool that provides blazing-fast database cloning and branching for any PostgreSQL database to build powerful development, test, QA, and staging environments. DLE can run dozens of independent clones of your database on a single machine, so each engineer or automation process works with their own database provisioned in seconds without extra costs. Data size and the number of snapshots/branches are virtually unlimited.

This release focuses on improving the admin experience during DLE configuration and troubleshooting. The full list of changes you can find in Release Notes.

Improved configuration and troubleshooting

DLE UI now has two new tabs: "Logs" and "Configuration". They help DLE admins troubleshoot issues with database refresh, adjust configuration, and make another attempt to get data without the need to use SSH.

DLE UI new tabs: Logs and Configuration

For logical mode (dump/restore), it is now possible to observe the current activity on both source and target sides:

DLE logical data provisioning activity

Postgres clone errors are now stored in a special "diagnostic" directory (see new configuration section – diagnostic) that allows analyzing them even if the corresponding Postgres clone was already deleted or lost.

More flexibility for schema and data patching

The configuration subsection queryPreprocessing is now present in the section logicalRestore, in addition to sections logicalSnapshot and physicalSnapshot. This can be helpful, for example, to mitigate errors related to CREATE POLICY and missing users – the queries provided in logicalRestore / queryPreprocessing are executed right before schema and data restoration attempt, so one can create "helper" database objects before the main body of the schema is created. For convenience, it is now also possible to provide inline SQL in queryPreprocessing in any section, instead of a path to SQL queries, for example:

- logicalRestore
- logicalSnapshot
queryPath: ""
maxParallelWorkers: 2
inline: |
inline: |
TRUNCATE audit_log;

Recently released PostgreSQL 15 is now fully supported as well as all previous versions starting with 9.6. The full list of supported PostgreSQL versions and extensions available in the default Docker images can be found in the docs).

Demo DLE

You can see new UI working with Demo DLE: (token: demo_token).

DLE in AWS Marketplace is GA

The AWS Marketplace version of Database Lab is now GA, and it's already updated to version 3.2. This offering is equipped with Standard license that includes guaranteed support from, simplified setup, embedded monitoring system (Netdata), optional SSL. Paying less than for an RDS clone, you can have dozens of full-size clones running on a single machine with DLE. This short video demonstrates the steps of installation and configuration of DLE for a 100 GiB RDS database:

You can try out installing DLE from AWS Marketplace for your database here:

Community news:

  • 🌠 DLE repository on GitHub reached 1.4k stars; many thanks to everyone who supports the project in any way
  • 📈 The Twitter account has reached 800 followers – please follow @Database_Lab
  • 🎉 DLE now has 19 contributors. More contributions are welcome! See "good first issues"
  • 🥇 Please consider various ways to contribute – read

Further reading


To get help, reach out to the team and the growing community of Database Lab users and contributors:

Request for feedback and contributions

Feedback and contributions would be greatly appreciated:

Like Database Lab? Give us a GitHub star:

Share this blog post:

Nikolay Samokhvalov
Nikolay Samokhvalov

CEO & Founder of

Working on tools to balance Dev with Ops in DevOps

Database Lab
Database Lab by

An open-source experimentation platform for PostgreSQL databases. Instantly create full-size clones of your production database and use them to test your database migrations, optimize SQL, or deploy full-size staging apps.