November 2023

Figuring out the upgrade path for AWS RDS from PostgreSQL 12.14 to PostgreSQL 16.1

These are my notes on figuring out an upgrade path for the FreshPorts PostgreSQL 12.14 database hosted on Amazon RDS. Most of this is based on Upgrading the PostgreSQL DB engine for Amazon RDS The sections of this post relate to the sections found at the above URL. First, I installed the AWS CLI (via py39-awscli, created an Access Key for my AWS login, and ran: Note that on line 4 I did […]

Figuring out the upgrade path for AWS RDS from PostgreSQL 12.14 to PostgreSQL 16.1 Read More »

Bacula: Moving from 9.x to 13.x and upgrading the PostgreSQL database

I have been using Bacula since 2004. It is my backup solution of choice, not only because it has a PostgreSQL backend, but it is flexible, robust, and reliable. I, on the other hand, have long ignored recent releases. I’m using Bacula 9.6.7 (released on 2021-01-26), roughly 3 years ago. Today, I started the upgrade to 13.0.1 (still not the latest release, but that’s because of a minor compile issue, not yet resolved;

Bacula: Moving from 9.x to 13.x and upgrading the PostgreSQL database Read More »

I figured out why pg_dump was failing with PostgreSQL 15-16

In recent blog post, I outlined a problem I hit with pg_dump. Specifically, pg_dump was picking up and using ~/.pgpass with pg_dump from PostgreSQL 12-14, but with PostgreSQL 15-16, it was failing. In this blog post: FreeBSD 13.2 PostgreSQL server 12 / 16 PostgreSQL client 12-16 Bacula 9.6.7 Today we figured out why: $HOME. $HOME for the script was set to / In PostgreSQL < 15, the code used the database to determine

I figured out why pg_dump was failing with PostgreSQL 15-16 Read More »

While restoring my PostgreSQL database to a new FreeBSD server, I discovered the wrong database server in a configuration file

Lately, I’ve been preparing to move from PostgreSQL 12 to PostgreSQL 16 – my main developement database server at home needs to get updated. The goal: migrate each database from the old host (running PostgreSQL 12) to the new host (running PostgreSQL 16) using pg_dump and pg_restore. Today, I decided to migrate the Bacula database. I ran a pg_dump on pg02 today. Then a pg_restore on pg03. That took about 6 hours I

While restoring my PostgreSQL database to a new FreeBSD server, I discovered the wrong database server in a configuration file Read More »

pg_dump: error: connection to server failed: fe_sendauth: no password supplied

FYI, this problem has been solved and described in I figured out why pg_dump was failing with PostgreSQL 15-16. This morning I encountered this error message: In this post: FreeBSD 13.2 PostgreSQL 12.16 (server – pg02) PostgreSQL 16.1 (client – dbclone) See also While restoring my PostgreSQL database to a new FreeBSD server, I discovered the wrong database server in a configuration file. The backstory: dbclone dumps the bacula database hosted on pg02.

pg_dump: error: connection to server failed: fe_sendauth: no password supplied Read More »

Jails with embedded, but not jailed, ZFS datasets – how to mount/umount – corrected

This is a rewrite of Jails with embedded, but not jailed, ZFS datasets – how to mount/umount. First, this is not about jailed ZFS datasets. I use them for FreshPorts, but that’s not I’m going to talk about here. In this post: FreeBSD 13.2 This is my example: [22:25 r730-03 dvl ~] % zfs list | grep bacula-sd-04 data01/bacula-volumes 12.1T 4.18T 96K /jails/bacula-sd-04/usr/local/bacula/volumes data01/bacula-volumes/DiffFile 109G 915G 109G /jails/bacula-sd-04/usr/local/bacula/volumes/DiffFile data01/bacula-volumes/FullFile 4.00T 2.00T 3.89T /jails/bacula-sd-04/usr/local/bacula/volumes/FullFile

Jails with embedded, but not jailed, ZFS datasets – how to mount/umount – corrected Read More »

Scroll to Top