Am Sonntag, 7. April 2019, 16:40:00 CEST schrieb stakanov:
In data domenica 7 aprile 2019 15:31:33 CEST, Hans-Peter Jansen ha scritto:
Am Montag, 1. April 2019, 11:51:39 CEST schrieb Wolfgang Bauer:
Am Sonntag, 31. März 2019, 22:40:41 schrieb Hans-Peter Jansen:
Will try Postgres, then.
Done that now, and guess what, switching to Postgres really made a difference!
Not only memory-wise, but also performance-wise. I never found kmail opening/ switching huge folders that fast.. (and no other MUA, that I tested,
... is on the same street with kmail anyway. Again, with huge mailboxes!
On that behalf, I found it uttermost difficult to get clear(!) indications about save practices and their implications with postgres, when using kmail/ akonadi locally.
Well, here we go: # switch to postgres root$ zyp in postgresql-server libQt5Sql5-postgresql akonadictl stop #stop all akonadi users psg 'kmail|akonadi|mysql' #kill akonadi mysql server instance cat > .config/akonadi/akonadiserverrc << EOF [Debug] Tracer=null [%General] Driver=QPSQL [PSQL] StartServer=true Name=akonadi EOF rm -r .local/share/akonadi akonadictl start # postgres update https://userbase.kde.org/Akonadi/Postgres_update
This is substantially the main reason why I switched back to Mysql. It was not clear to me with what policy I would have guaranteed a safe postgres installation for only local use with akonadi. Some say: set a password, some don't.
Using that procedure results in: cat ~/.local/share/akonadi/db_data/pg_hba.conf # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 trust # Allow replication connections from localhost, by a user with the # replication privilege. local replication all trust host replication all 127.0.0.1/32 trust host replication all ::1/128 trust At least on TW. If somebody is able to access your database on localhost or unix domain sockets, you're busted anyway. So, what you should care about are major Postgres upgrades: it comes down to installing both versions, and manually upgrade the database, which also means, that you need enough space for both versions temporarily. Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org