Neues vom PostgreSQL Planet

This might not interest many of you, but I recently heard about at least two people that stumbled upon the problems I did, so I figured I can write about problems we discovered, and how we solved them (or not). When we began our journey, the latest Pg was 14.x, that's why we're upgrading to … Continue reading "A tale about (incomplete) upgrade from PostgreSQL 12 to 14"

Introduction We are thrilled to announce the release of pg_cirrus! First of all, you might be wondering what “cirrus” means. The term refers to the thin and wispy clouds that are often seen at high altitudes. pg_cirrus is a simple and automated solution to deploy highly available 3-node PostgreSQL clusters with auto failover. It is […]

I recently released PostGIS 3.3.3. bundle for Windows which is available on application stackbuilder and OSGeo download site for PostgreSQL 11 - 15.

This month’s PGSQL Phriday topic is “database change management”, proposed by Dian Fay.

While I’ll try to make this topic about performance (as I always do) let me first embark on a quick trip down memory lane.

The host for PGSQL Phriday #009 is Dian Fay, who has asked us to discuss how we manage database changes. Oh my, Dian picked a topic that’s near and dear to me. In fact, one of my (still visible) T-SQL Tuesday blog posts was about this very topic… 7 years ago! Quick aside: For those ... Read more

The invitation this month for #PGSqlPhriday comes from Dian Fay. The topic is pretty simple, database change management. Now, I may have, once or twice, spoken about database change management, database DevOps, automating deployments, and all that sort of thing. Maybe. Once or twice. OK. This is my topic. I’ve got some great examples on […]

The post PGSQL Phriday #009: On Rollback appeared first on Grant Fritchey.

One of the big topics in Postgres is bloat. It is something that every DBA comes across and in fact we have a few good posts on how to work with bloat in our blog. 

Update-heavy tables is a special case of data that due to business requirements needs to be updated frequently to stay relevant. Autovacuum may be a good solution for table bloat (you can check this post describing how to do that), however it does not help with index bloat. 

This post is for subscribers

Type your email…

Subscribe

I've used several migration frameworks in my time. Most have been variations on a common theme dating back lo these past fifteen-twenty years: an ordered directory of SQL scripts with an in-database registry table recording those which have been executed. The good ones checksum each script and validate them every run to make sure nobody's trying to change the old files out from under you. But I've run into three so far, and used two in production, that do something different.

Postgres 16 is hot off the press with the beta release last week. I am really excited about the new feature that allows logical replication from standbys, allowing users to:

The news today is that SQL:2023, the new version of the SQL standard, has been published by ISO.

Here are links to the parts on the ISO web site:

If nodes in a database cluster get out of sync, the inconsistency can cause data corruption. This blog describes what to watch out for.

The post Data inconsistency in highly available PostgreSQL clusters appeared first on Stormatics.

PostGIS excels at storing, manipulating and analyzing geospatial data. At some point it's usually desired to convert raw spatial data into a two-dimensional representation to utilize the integrative capabilities of the human visual cortex. In other words, to see things on a map.

Thanks to some help from my co-workers Elizabeth and David Christenson and their son, I got my site migrated from Wordpress to Hugo! Being a DBA, you’d think I wouldn’t mind having a database backing my website, but the simplicity of managing a static site like Hugo was much more appealing at this point. With a new site that’s far easier to manage, I’m hoping that will motivate me to get back to writing new content on a regular basis.

This is part of a series I began in 2018, documenting my journey from SQL Server to PostgreSQL. As someone that’s been through the process before, my hope is that these discussions will help mitigate some of the surprises and help you get up to speed faster. Today, I’m going to dig into how PostgreSQL ... Read more

It’s annoying to get error messages caused by encoding problems. But it is more annoying not to get error messages and end up with bad data in the database. I’ll show you how to fix bad encoding.

PostgreSQL Person of the Week Interview with Carlos Chapi: My name is Carlos Chapi, I’m a computer engineer from Ecuador and, at the time of writing this, I’m 33 years old. I also recently got married so I’m getting used to that too.

Disaster recovery is not optional for businesses operating in the digital age. With the ever-increasing reliance on data, system outages or data loss can be catastrophic, causing significant business disruptions and financial losses.

What’s the fastest compiler for PostgreSQL? Let’s take a look.

psql, the database client for PostgreSQL has, since forever, support for variables. These let you write certain queries in a way that is safe even when getting params from “outside". Let's see what can be done with it… To use them, we first need to know how to set them. For this, we have multiple … Continue reading "Variables in psql, how to use them?"