New name: DBLab EngineThe new name for the Database Lab Engine is "DBLab Engine". Updates are currently underway across our materials to reflect this change. To align with this change, we have introduced specific domains for the product:dblab.dev anddblab.sh. For ease of access, we have established the following short URLs: 
New contributors🙇 Many thanks to our first-time contributors:@mbobin,@TheLiamGuy,@gromsterus,@ibash,@byx01,@davidsvenson. By the numbersThank you for the support! New DBLab SE installerWe've expanded the installation options for DBLab SE. Besides its presence inthe AWS Marketplace, you can now seamlessly install DBLab SE directly fromthe Postgres.ai Console. 
This setup is entirely automated and can be used anywhere: - For those who have existing machines, we support the "BYOM" (Bring Your Own Machine) method
- If you're utilizing AWS, GCP, DigitalOcean, or Hetzner Cloud, the installer handles resource provisioning—including VMs, disks, and more—automatically.
Check outthe updated tutorial. Migration notesFor those considering an upgrade, we recommend executing a fresh installation of DBLab. At present, we don't have automation in place for upgrades. If you need to update an existing DBLab installation, it's essential to stop and remove the current containers. Then, initiate a fresh start of the DBLab container using the3.4.0 tag. More details can be found inthe docs. Before initiation, ensure you've adjusted the DBLab configuration as outlined below. Postgres imagesThere is a new method for running clones with customized port and socket directories. Please note that this is NOT backward compatible with previous versions of the Postgres images that DBLab utilized. It is crucial to ensure thedockerImage options utilize tags with the-0.3.0 suffix or later, such aspostgresai/extended-postgres:15-0.3.0 (details can be found inthis MR). Global telemetryTheglobal.telemetry subsection has been deprecated and removed. The control to activate/deactivate telemetry has been relocated to theplatform section: platform:url:"https://postgres.ai/api/general"enableTelemetry:true PlatformFrom versionv3.4.0 onward, theplatform section is enabled by default. If either theaccessToken ororgKey keys aren't empty, ensure theurl parameter is specified; otherwise, the DBLab instance will not initialize. By default, neitheraccessToken nororgKey are defined when in case of self-managed installations. platform:url:"https://postgres.ai/api/general"enableTelemetry:true# orgKey: "org_key"# accessToken: "platform_access_token" Docker mountsPlease omit the following Docker mount directives during container startup, as they are no longer necessary: --volume /sys/kernel/debug:/sys/kernel/debug:rw \ --volume /lib/modules:/lib/modules:ro \ --volume /proc:/host_proc:ro \ ChangelogNew features- Configuration: new option
ignoreErrors in subsectionslogicalDump andlogicalRestore to allow not to interrupt the process of dump/restore in case of errors -https://gitlab.com/postgres-ai/database-lab/-/merge_requests/699,https://gitlab.com/postgres-ai/database-lab/-/merge_requests/700,https://gitlab.com/postgres-ai/database-lab/-/merge_requests/730 - Configuration: new option
skipPolicies in subsectionlogicalRestore to allow to skip policies (CREATE POLICY) during restore process, to avoid errors likepolicy "xxx" for table "yyy" already exists:https://gitlab.com/postgres-ai/database-lab/-/merge_requests/769 - Configuration: new option
cloneAccessAddresses in sectionprovision to control port publishing for clone containers; now limited to127.0.0.1 by default; support multiple addresses and IPv6:https://gitlab.com/postgres-ai/database-lab/-/merge_requests/786 - UI: Improved Logs view with log filters -https://gitlab.com/postgres-ai/database-lab/-/merge_requests/672,https://gitlab.com/postgres-ai/database-lab/-/merge_requests/702
- CLI: ARM / Apple silicon (M1, M2) support for DBLab CLI binaries -https://gitlab.com/postgres-ai/database-lab/-/merge_requests/719,https://gitlab.com/postgres-ai/database-lab/-/merge_requests/733
- API: DBLab v3.4.0 API specification updated and is now published onapi.dblab.dev:https://gitlab.com/postgres-ai/database-lab/-/merge_requests/747
- Numerous updates to Postgres images
- supported Postgres major versions: 9.6-15
- image tags:
9.6-0.3.0 ...15-0.3.0;⚠️ older tags won't work with DBLab 3.4.x pgvector extension added to- existing extension upgraded (docs)
- special images for DBLab SE/EE (with some extension being mocked): RDS Postgres, Aurora, GCP Cloud SQL, Supabase, Timescale, Heroku, PostGIS
- New installer for DBLab SE, available atConsole.Postgres.ai, and simplified configuration for various managed PostgreSQL services such as AWS RDS, GCP Cloud SQL, Supabase, Heroku - various MRs
Improvements and fixesInternal changesFull diffDiff between versions v3.3.0 and v3.4.0:v3.3.0...v3.4.0 Where to start / get helpProvide feedback, contributeWe greatly value your feedback. Connect with us via: Additional resources where you can hear more information about DBLab and Postgres: Interested in giving back to the project? Here's how you can make an impact: |
