Mounting the ZFS datasets mysql-innodb-data and mysql-innodb-logs outside of /var/db/mysql, then deploying them to db-B-001: operation completed and functional.

Deployed on WindRiver.

Avancement sur T2074

Deployed for WindRiver, server now runs on 17.6.

Taking this, we've PostgreSQL deinstalled on WindRiver; as we're on a UNIX system, it still runs without any issue as long as it doesn't need to load dynamically a library, accepts connection, serves traffic but software isn't there anymore.

In T2185#33876, @dereckson wrote:

Each test run produces this:

Nov 11 02:29:33 windriver postgres[63389]: [19-1] 2025-11-11 02:29:33.804 UTC [63389] ERROR:  relation "nonexisting" does not exist at character 13
Nov 11 02:29:33 windriver postgres[63389]: [19-2] 2025-11-11 02:29:33.804 UTC [63389] STATEMENT:  DELETE FROM nonexisting
Nov 11 02:29:34 windriver postgres[63402]: [19-1] 2025-11-11 02:29:34.181 UTC [63402] ERROR:  relation "nonexisting" does not exist at character 15
Nov 11 02:29:34 windriver postgres[63402]: [19-2] 2025-11-11 02:29:34.181 UTC [63402] STATEMENT:  SELECT * FROM nonexisting
Nov 11 02:29:34 windriver postgres[63403]: [19-1] 2025-11-11 02:29:34.209 UTC [63403] ERROR:  relation "nonexisting" does not exist at character 15
Nov 11 02:29:34 windriver postgres[63403]: [19-2] 2025-11-11 02:29:34.209 UTC [63403] STATEMENT:  SELECT * FROM nonexisting
Nov 11 02:29:34 windriver postgres[63408]: [19-1] 2025-11-11 02:29:34.357 UTC [63408] ERROR:  relation "not_existing_table" does not exist
Nov 11 02:29:34 windriver postgres[63408]: [19-2] 2025-11-11 02:29:34.357 UTC [63408] STATEMENT:  TRUNCATE not_existing_table
Nov 11 02:29:34 windriver postgres[63409]: [19-1] 2025-11-11 02:29:34.385 UTC [63409] ERROR:  relation "not_existing" does not exist
Nov 11 02:29:34 windriver postgres[63409]: [19-2] 2025-11-11 02:29:34.385 UTC [63409] STATEMENT:  TRUNCATE not_existing
Nov 11 02:29:34 windriver postgres[63416]: [19-1] 2025-11-11 02:29:34.591 UTC [63416] FATAL:  password authentication failed for user "notexisting"
Nov 11 02:29:34 windriver postgres[63416]: [19-2] 2025-11-11 02:29:34.591 UTC [63416] DETAIL:  Role "notexisting" does not exist.
Nov 11 02:29:34 windriver postgres[63416]: [19-3]       Connection matched pg_hba.conf line 22: "host    all             all             127.0.0.1/32            scram-sha-256"

I guess we could avoid to post PostgreSQL logs directly in /var/log/messages.

Each test run produces this:

Actually, we use the same database name than for MariaDB / MySQl:

Write is working.

Wiki is now using wolfplex_wiki database.

Import to wolfplex_wiki database done.

Wolfplex wiki is in read-only mode.

Alternatively, we made a lot of progress on this in T2124.

For reference, the configuration contains max_binlog_size = 1000M. This only affects the maximal size of ONE log file, but it can create as many as needed.

For dbserver-mysql role, configuration is located at roles/dbserver-mysql/mysql-server/files/conf.d/server.cnf

I've added documentation to https://agora.nasqueron.org/Operations_grimoire/FreeBSD#PostgreSQL without real conviction.

When upgraded to FreeBSD 14, we lost this.

What if we plan a brainstorming session where we put cards on a wall, one card per feature we'd like to see on the app?

Not sure each service has an IP, or only an IP. For those we do, what we do with the IP?

In T1842#27788, @dereckson wrote:

Can you give an example of what you wish to store as information and how you wish to use it?

Can you give an example of what you wish to store as information and how you wish to use it?

@dereckson hey, we forgot about id addresses, so do you think it would be wise to simply add a new column in the service table?

Packages required to build it ourselves:

upstream https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269115

As a minimum, to have somewhere (a reports repository?) where we can write those report queries could already be useful, so we don't lose them.