Skip to content

v2.4.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Aug 13:13
· 2 commits to master since this release
v2.4.1
0982f16

dbdeployer v2.4.1

A focused patch release that makes deploy replication fast again and rounds out PostgreSQL deployment flexibility. No breaking changes — a drop-in replacement for v2.4.0.

Replication deployments are fast again

In v2.4.0, dbdeployer deploy replication could take around 5 minutes to finish, even for a small master + replica topology. We traced this to two readiness waits that kept polling long after there was anything left to wait for — one of them ran on every node even for plain MySQL, where it could never succeed.

v2.4.1 removes that wasted waiting: the same deployment now completes in roughly 10 seconds, and the replica is verified to be serving queries before the command returns.

If you sidestepped deploy replication because of the v2.4.0 delay, it is worth another try.

More control over PostgreSQL deployments

dbdeployer deploy postgresql now respects the placement and credential flags that MySQL deployments already honored:

  • --sandbox-home — where the sandbox is created
  • --port — which port to bind
  • --sandbox-directory — the sandbox folder name
  • --db-user / --db-password — the initial superuser and its password

This makes it practical to run several isolated PostgreSQL sandboxes side by side (for example, one per project or branch) instead of everything landing in a single fixed pg_sandbox_<port> directory. When you pass no flags, behavior is exactly as before.

A little polish

MariaDB sandboxes now greet you with a MariaDB prompt by default (instead of mysql), so it is immediately obvious which flavor you are connected to.

Upgrading

No action required and no configuration changes. Binaries for Linux and macOS (amd64/arm64) are attached below, along with checksums.txt.

Full changelog: v2.4.0...v2.4.1

Assets 7
Loading