In today's discourse, we delve into the intricacies of accessing Snowflake via the Trino project. This article illuminates the seamless integration of Trino with Snowflake, offering a comprehensive analysis of its benefits and implications.
This is a long anticipated third article on optimizing pgbench for CockroachDB. I've been wanting to write a follow up ever since I learned about new improvements in the next release of CockroachDB.
CockroachDB Dedicated comes with TLS enabled by default. At the minimum, a certificate authority is needed to authenticate. A customer was having issues using Flyway and TLS.
As of this writing, CockroachDB does not have official support for protobuf payload as part of change data capture. Today, I am going to demonstrate a feature that may or may not land in CockroachDB proper. The product team is looking into viability of the feature before we can officially support it.
This is my series of articles covering short "Today I learned" topics as I work with CockroachDB. Today, we're diagnosing cert issues, looking at client verification of server certificates differences in the cockroach
and the psql
clients, and checking the node and the CA certificate expiration programmatically.
Today, I am looking at a database caching product called PolyScale.ai.
I've been experimenting with CockroachDB high availability scenarios and fault domains. CockroachDB relies on load balancer to provide client fault tolerance. Today, I'd like to look at a load balancer as the single point of failure. To my knowledge, load balancer high availability is not discussed in any of the existing CockroachDB documentation.
I've been experimenting with PgCat which markets itself as a PostgreSQL pooler and proxy (like PgBouncer) with support for sharding, load balancing, failover and mirroring.