postgresql_cluster is now autobase – same powerful platform, bold new name!
We’re still the same powerful automated database platform for PostgreSQL®, now with a fresh name, a new logo, and bold ambitions.
Autobase embodies automation and flexibility in database management. Our new logo—a cloud icon with arrows pointing up and down—perfectly captures seamless adaptability: effortlessly host your data in the cloud or on-premises and migrate between them. This design symbolizes autobase’s ability to integrate into any infrastructure, providing full control over your data—no limits, no compromises.
Discover the future of Postgres automation at autobase.tech
postgresql_cluster is now autobase – same powerful platform, bold new name!
We’re still the same powerful automated database platform for PostgreSQL®, now with a fresh name, a new logo, and bold ambitions.
Autobase embodies automation and flexibility in database management. Our new logo—a cloud icon with arrows pointing up and down—perfectly captures seamless adaptability: effortlessly host your data in the cloud or on-premises and migrate between them. This design symbolizes autobase’s ability to integrate into any infrastructure, providing full control over your data—no limits, no compromises.
Discover the future of Postgres automation at autobase.tech
Fun fact: psql has a syntax through which one can use a form of prepared statements to avoid exploding when the password contains sql-sensitive characters[1]: https://www.postgresql.org/docs/17/app-psql.html#APP-PSQL-OP... and https://www.postgresql.org/docs/17/app-psql.html#APP-PSQL-IN... although regrettably it is not compatible with the "-c" invocation for some terrible reason, thus requiring the SQL to actually come from stdin:
1: https://github.com/vitabaks/autobase/blob/e93fbe0c667c18a24e...Thanks. Feel free to suggest a PR.