Introducing Crunchy Data Warehouse: A next-generation Postgres-native data warehouse. Crunchy Data Warehouse Learn more
Bob Pacheco
Bob Pacheco
Many applications running on Kubernetes will send their output to standard error ( ) and standard out ( ). This is a convenient location for log aggregators to collect and consolidate logs. However, some applications like Postgres write their logs to disk so getting the Postgres logs to the log aggregator requires a few special tricks. Crunchy Postgres for Kubernetes recently introduced support for sidecar containers for both Postgres and PgBouncer pods. A sidecar is a container that runs alo...
Read MoreJoseph Mckulka
Joseph Mckulka
Crunchy Postgres for Kubernetes can be used for cross-datacenter streaming replication out of the box. With so many folks asking for cross-cloud / cross-datacenter replication, we wanted to give people a large explanation of how that works. For this post, we use streaming replication, and prioritize reducing latency and adding stability. Cross-cloud streaming replication can be used: • To enable multi-cloud disaster recovery • For moving clusters between cloud providers • For moving clusters be...
Read MoreAndrew L'Ecuyer
Andrew L'Ecuyer
Lukas Fittl recently posted one of his 5 minutes of Postgres videos about his experimentation with different Kubernetes Postgres Operators: Postgres on Kubernetes, choosing the right operator, and handling major version upgrades . One passage about version updates caught my interest: The other article I found interesting was this post by Andrew from the Crunchy Data team , where he describes how the PGO operator now makes it easy to do major version upgrades. This is actually pretty cool. I th...
Read MoreGreg Nokes
Greg Nokes
We are excited to announce the release of Crunchy Postgres for Kubernetes version 5.2. We have been hard at work on a lot of new features we cannot wait to get into your hands. You can get started on version 5.2 from our container portal or the get started tutorial . We have decided to highlight a few of our favorite features today. First, we are very excited to release the first iteration of our CLI for PGO v5, . Our CLI is designed as a plugin. You can get it here and you can use it...
Read MoreRekha Khandhadia
Rekha Khandhadia
Recently I worked with one of my Crunchy Data PostgreSQL clients on implementing caching for pg_tileserv. pg_tileserv is a lightweight microservice to expose spatial data to the web and is a key service across many of our geospatial customer sites. pg_tileserv can generate a fair amount of database server load, depending on the complexity of the map data and number of end users, so putting a proxy cache such as Varnish in front of it is a best practice. Using Paul Ramsey's Production PostGIS...
Read MoreBrian Pace
Brian Pace
Getting frequent copies of data for development and testing purposes is a very common use case with our enterprise customer base. We have customers getting data copes for each sprint or development cycle. This increasing data copy problem can put a strain on IT budgets with the storage consumed and the hours spent performing database refreshes. A common process is to build or refresh environments using database restores. There can be some challenges with this approach. First, the data must be mo...
Read MoreAndrew L'Ecuyer
Andrew L'Ecuyer
Modern day production ready Postgres solutions require quite a bit of sophistication and automation. Changes need to be applied in a uniform and safe way. DevOps and SRE teams need to be in control system updates while limiting disruption to their users. With the release of PGO v5.1 , we are excited to announce enhancements in each of these areas. Not only does PGO v5.1 now automatically rollout all PostgreSQL configuration changes, but it allows you to protect your running databases against ou...
Read MoreAndrew L'Ecuyer
Andrew L'Ecuyer
Recently, there has been a bit of a debate here at Crunchy Data around SQL editors. While some members of the Crunchy Team such as Elizabeth ( @e_g_christensen ) prefer pgAdmin 4, others such as Craig (@ craigkerstiens ) prefer using psql . And one the great things about the PostgreSQL ecosystem is that there is no right answer to this debate! Instead, you have choice and flexibility when it comes to finding and using the tools that meet your specific database development and/or management need...
Read MoreAndrew L'Ecuyer
Andrew L'Ecuyer
Whether upgrading PGO itself, or upgrading the PostgreSQL databases PGO manages, seamless upgrades should be a core feature for any cloud or Kubernetes-based database solution. As a result, one of the goals when we set out to build version five of PGO, the Postgres Operator from Crunchy Data, was to provide a seamless and user-friendly upgrade experience. Today we’re excited to introduce support for major version PostgreSQL upgrades in PGO v5.1. Using the new PGUpgrade API, you can now seamlessl...
Read MoreAndrew L'Ecuyer
Andrew L'Ecuyer
A colleague of mine recently tweeted the following, highlighting the challenges often associated with database upgrades: Last week had 3 calls before noon of people having difficulty with database upgrades and connection scaling. Two things that should be staples for a database provider and they had no idea until 6 months in when they tried to upgrade. As an industry we can build better. — Craig Kerstiens (@craigkerstiens) March 28, 2022 When I saw that tweet, I couldn’t help but appreciate the...
Read More