When it comes to database performance, many think they are solving technical problems, but are solving a money problem. There are 2 phases to database-cost management, and understanding which phase you are in will help you understand your options for growth.
A review of PGO 5.1 features including rolling database restarts, pod disruption budgets, and manual switchovers/failovers.
Crunchy Data is excited to release a new open source tool, Exporter2Perfdata. This connects Prometheus Exporters with Icinga2/Nagios. This also allows pgMonitor users to connect monitoring information from Prometheus to Icinga2 and Nagios.
David optimizes a slow query by splitting up a left join into two calls and using UNION ALL to combine them. The proof is in the pudding.
Use your spatial data with this lightweight web server to make an instant heatmap! Paul sets up a demo using locations, name data, and our new container apps feature to run the pg_featureserv right inside the database.
Which of my applications ran this SQL statement? Use SQL comments to track which application ran which queries.
Keith offers a high level review of the vectors of attack on databases and database encryption types including Data-At-Rest, Data-In-Transit, and Data-In-Use.
For developers, databases are basically magic. Like Penn & Teller, this blog post is set to break the illusion. Databases are just like any other code, they have algorithms and processes. These algorithms and processes are meant to improve performance, but can cause limitations if they are not expected.
Need a GUI for your Postgres cluster? PGO 5.1 introduces a new feature to let you create a pgAdmin 4 pod alongside your other database services managed by the Kubernetes Operator.
Have too much static data? Paul has a idea of moving some of it to a datalake. He provides a walk-through of setting up Parquet with Postgres using the parquet_fdw.
Today we’re excited to introduce support for major PostgreSQL upgrades in PGO v5.1. Using the new PGUpgrade API, you can now seamlessly upgrade your clusters across major versions of PostgreSQL.
We're excited to announce the general availability of version 5.1 of PGO, the open source Postgres Operator from Crunchy Data. In addition to providing a seamless upgrade experience across both PGO and PostgreSQL versions, this feature-packed release also introduces many powerful new capabilities.
Load some PostGIS data, import a shape file and publish a map to the web. Easy peasy lemon squeezy.
With Postgres Container Apps you can, from directly inside Postgres with a simple function call, spin up a container that is running right alongside your Postgres database!
In this post we'll show some examples of spatial filtering using CQL with pg_featureserv.
Paul takes a recent example of GPU-assisted spatial joins project to see how PostGIS stacks up in the same situation. He goes through the steps of joining a large record set of parking data with neighborhood data.
Recently Crunchy Data added pg_featureserv support for most of CQL2. Here we'll describe the powerful new capability it provides.
Fun with PostgreSQL! Using the French Wordle list, this post shows you some sql to find out the most often used letters in a table, how to reduce possibilities once you’ve found some letters, and how to solve wordle puzzles using the back end.
New feature release for PGO v5.0.5 Initializing your Postgres database with backups from AWS S3, GCS or Azure.
Risk management for Postgres. A guide to changing application user permissions so they can't delete your production database.