I want planning on running bsdinstall. However, since I’m doing a zfs send | recv, there’s no reason why not.

I’ll have the benefit of moving to entirely new media. The original boot drives will be untouched.

That’s a good point. Thanks.

It works. Took me a while to get the host to boot.

oh, and:

heathen.

But it's not. It's the same risk level, is it not, as 4x 2TB drives in the same configuration. Right?

..after having ensured that all client libraries in use are new enough to support SCRAM, set password_encryption = 'scram-sha-256' in postgresql.conf, make all users set new passwords, and change the authentication method specifications in pg_hba.conf to scram-sha-256.

2/2

Here's what the test script once this morning:

# ${SUDO} -u postgres ${PSQL} postgres < ${GLOBALS}.sql

Here is what it will do tomorrow:

${GREP} -vi 'CREATE TABLESPACE' ${GLOBALS}.sql | ${SUDO} -u postgres ${PSQL} postgres

2/2

Let's see what tomorrow brings.

1 - www.postgresql.org/docs/current...

5/5

The diff:

[11:13 dbclone dvl ~/bin] % diff -N test-postgresql-backups.sh~ test-postgresql-backups.sh
11c11
< PGRESTORE="/usr/local/bin/pg_restore -j 8"
---
> PGRESTORE="/usr/local/bin/pg_restore -j 8 --no-tablespaces"
[11:13 dbclone dvl ~/bin] %

4/5

This morning I consulted the man page[1] and found:

--no-tablespaces
Do not output commands to select tablespaces. With this option, all objects will be created in whichever tablespace is the default during restore.

3/5