This time we talk about using ltree as an alternative to PostgreSQL cursors.

PostgreSQL has quite a number of better algorithmic alternatives to cursors. We'll start by examining the advantages of Common Table Expressions.

Binary Objects in PostgreSQL definitely have caveats, and don't behave the way you might expect coming from an Oracle background. This article demystifies the Blob, gives some practical advice for dealing with them, and improves your philosophy.

PostgreSQL has quite a few compelling advantages, some of which are not found in any other database management system. This article will outline the ones that are most interesting to the Oracle developer seeking to do a migration or investigate alternatives for new development. To prevent this article from becoming another list of PostgreSQL features, it will stick to the features that...

This article provides the Oracle database administrator with equivalent PostgreSQL architecture knowledge. The process is a bit loose, but it is sufficient to bootstrap the concepts that are transferable and identify the ones that are not.

And now we arrive at the second article in our migration from Oracle to PostgreSQL series. This time we’ll be taking a look at the START WITH / CONNECT BY construct. In Oracle, START WITH / CONNECT BY is used to create a singly linked list structure starting at a given sentinel row. The linked list may take the form of a tree, and has no balancing requirement. To illustrate, let’s start with a...

We find ourselves at the third article in the Oracle migration series. This time, we look at those strange operators that modify the WHERE clause criteria in Oracle (+). Like everything else, PostgreSQL has a solution for that.

This article is the first in a series about migrating from Oracle to PostgreSQL. We will attempt to cover each of the topics of migration in some amount of depth and provide multiple options to the same issues and architectures. For this first article, we’ll take a look at Oracles’ ROWNUM and ROWID.

The title is not clickbait or hyperbole. I intend to prove that by virtue of both design and implementation that PostgreSQL is objectively and measurably a better database than anything currently available, with or without money considerations. How in the world can I claim and justify such a lofty statement? Read on, gentle nerd. I promise that your time will not be wasted. Transparent Security...

K-nearest neighbor answers the question of "What is the closest match?". PostgreSQL 12 can answer this question, and use indexes while doing it.