DBLab Engine v3.4.0
#180
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
New name: DBLab Engine
The 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.devanddblab.sh. For ease of access, we have established the following short URLs:curl -sSL dblab.sh | bash)demo-token)demo-token)New contributors
🙇 Many thanks to our first-time contributors: @mbobin, @TheLiamGuy, @gromsterus, @ibash, @byx01, @davidsvenson.
By the numbers
Thank you for the support!
New DBLab SE installer
We've expanded the installation options for DBLab SE. Besides its presence in the AWS Marketplace, you can now seamlessly install DBLab SE directly from the Postgres.ai Console.
This setup is entirely automated and can be used anywhere:
Check out the updated tutorial.
Migration notes
For 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 the
3.4.0tag. More details can be found in the docs. Before initiation, ensure you've adjusted the DBLab configuration as outlined below.Postgres images
There 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 the
dockerImageoptions utilize tags with the-0.3.0suffix or later, such aspostgresai/extended-postgres:15-0.3.0(details can be found in this MR).Global telemetry
The
global.telemetrysubsection has been deprecated and removed. The control to activate/deactivate telemetry has been relocated to theplatformsection:Platform
From version
v3.4.0onward, theplatformsection is enabled by default.If either the
accessTokenororgKeykeys aren't empty, ensure theurlparameter is specified; otherwise, the DBLab instance will not initialize. By default, neitheraccessTokennororgKeyare defined when in case of self-managed installations.Docker mounts
Please 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 \Changelog
New features
ignoreErrorsin subsectionslogicalDumpandlogicalRestoreto 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/730skipPoliciesin subsectionlogicalRestoreto 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/769cloneAccessAddressesin sectionprovisionto control port publishing for clone containers; now limited to127.0.0.1by default; support multiple addresses and IPv6: https://gitlab.com/postgres-ai/database-lab/-/merge_requests/7869.6-0.3.0...15-0.3.0;pgvectorextension added toImprovements and fixes
/statuswith proper messages - https://gitlab.com/postgres-ai/database-lab/-/merge_requests/696portPoolinclusive (previously, it was mistakenly exclusive, leading to unexpected behavior): https://gitlab.com/postgres-ai/database-lab/-/merge_requests/785Error response from daemon: Duplicate mount point: /var/lib/dblab/dblab_pool/dataset_1/dump/: https://gitlab.com/postgres-ai/database-lab/-/merge_requests/791Internal changes
trusted.gpg.dbecauseapt-keyis deprecated - https://gitlab.com/postgres-ai/database-lab/-/merge_requests/701Full diff
Diff between versions v3.3.0 and v3.4.0: v3.3.0...v3.4.0
Where to start / get help
demo-token)Provide feedback, contribute
We 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:
Beta Was this translation helpful? Give feedback.
All reactions