We at Crunchy Data put as much development effort into improving GEOS as we do improving PostGIS proper, because the GEOS library is so central to much geospatial processing.
The EXPLAIN command helps you look even closer into an individual query. If you're already proficient in EXPLAIN, great! Read on for an easy refresher. If you're less familiar with it, this will be a (hopefully) gentle introduction on what insights it might help provide.
Welcome to Episode 2 of the "Musings of a PostgreSQL Data Pontiff" series! In this installment I’m aiming to achieve three objectives.
This is the first in a series of blogs on the topic of using PostgreSQL for "data science". I put that in quotes because I would not consider myself to be a practicing "data scientist", per se. Of course I'm not sure there is a universally accepted definition of "data scientist". This article provides a nice illustration of my point.
With this release, we included features to streamline management of the Operator, added security features, and extra system metrics to enhance your high availability Kubernetes Postgres cluster. Let's take a look at what's new in the Postgres Operator 4.6!
Crunchy Data has recently announced an update to the CIS PostgreSQL Benchmark by the Center for Internet Security, a nonprofit organization that provides publications around standards and best practices for securing technologies systems.
How can you apply GitOps principles to running PostgreSQL on Kubernetes with Helm?
The page "Falsehoods Programmers Believe About Names" covers some of the ways names are hard to deal with in programming. This post will ignore most of those complexities, and deal with the problem of matching up loose user input to a database of names.
Today we are going to walk through some of the preliminary data shaping steps in data science using SQL in Postgres.
I want to work on optimizing all my queries all day long because it will definitely be worth the time and effort. That's a statement that has hopefully never been said. So when it comes to query optimizing, how should you pick your battles?
Recently I ran across grand sweeping statements that suggest containers are not ready for prime time as a vehicle for deploying your databases. The definition of "futile" is something like "serving no useful purpose; completely ineffective". See why I say this below, but in short, you probably are already, for all intents and purposes, running your database in a "container". Therefore, your resistance is futile.
As a GIS newbie, I've been trying to use local open data for my own learning projects. I've recently relocated to Tampa, Florida, and was browsing through the City of Tampa open data portal and saw that they have a Public Art map. That sounded like a cool dataset to work with but I couldn't find the data source anywhere in the portal. I reached out to the nice folks on the city's GIS team and they gave me an ArcGIS-hosted URL.
Learn how to use Kubernetes taints, pod tolerations, and node affinity for designing and deploying production PostgreSQL topologies.
When Linux detects that the system is using too much memory, it will identify processes for termination and, well, assassinate them. The OOM killer has a noble role in ensuring a system does not run out of memory, but this can lead to unintended consequences.
Deciding to use Postgres is a great start, we like to think it’s the right start. As to how best to deploy it, you have a number of options.
A step-by-step guide for how to setup PostgreSQL change data capture with Debezium and Apache Kafka.
How can you get PostgreSQL to use FIPS 140-2 crypto? The answer, to some extent, depends on how rigorously you need to be able to prove your answer. If the proof required is more than a casual check, the process is not well documented as far as I can tell. Therefore I will attempt to address that deficiency here.
Actionable steps on how to improve your Postgres database performance.
Deploy PostgreSQL clusters on Kubernetes with GitOps and the Postgres Operator!
Learn how to deploy pgBouncer with TLS connections in Kubernetes using the Postgres Operator!