Need advice about database design or query optimization? Add this tag.
This is a project-as-a-tag.
Need advice about database design or query optimization? Add this tag.
This is a project-as-a-tag.
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
Decreasing priority as no wheelwar will exist on db-A: php83-pdo_pgsql isn't declared there.
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