PostgreSQL

Moving the email notifications to the new server

Ever since the new server went into production, sometime in 2017, the notification emails, which tell you what has changed, have been coming from the old server. I never did that changeover. The old server was still processing incoming commits, so the notifications were accurate. However, new accounts would not get notifications and changes to […]

Moving the email notifications to the new server Read More »

procedure OK under 10.6 but starts acting up under 11.1

I originally documented this so I would have a reference while tracking down the problem. I have since solved the issue and you can jump to the bottom of this post to find the solution. What I do not know is why this was not an issue under PostgreSQL 10.6 but was under PostgreSQL 11.1.

procedure OK under 10.6 but starts acting up under 11.1 Read More »

Duplicate dependency issues – avoiding duplicate rows

Databases use relational integrity to enforce expected situations. A common scenario is duplicates. Case in point, I present the port_dependencies table: For those not familiar with FreeBSD ports, each port (you could also refer to them as a package or application) can have zero or more dependencies. The FreshPorts database extracts and lists these dependencies

Duplicate dependency issues – avoiding duplicate rows Read More »

When dependencies change, both ports need to be updated

FreshPorts uses a cache for every port page (e.g. https://www.freshports.org/sysutils/bacula-server/). When an update to a port occurs, we must clear the cache for that port. This sounds simple, and it is. The various ways in which updates occur complicates the situation. This post is all about fixing one edge case: the addition or removal of

When dependencies change, both ports need to be updated Read More »

Scroll to Top