Backstory: I had a debian 11 VPS. I installed the postgresql program from the debian 11 apt repo, back a few months ago. Back then, it was postgres 13 on the debian stable repos.
Fast forward couple months: debian 12 comes out. I do a “apt dist-upgrade” and in-place upgrade my VPS from debian 11 to debian 12. Along with this upgrade, comes postgresql 15 installed.
Now, fast forward couple more months: lemmy 0.18.3 comes out. I do not upgrade (I am on lemmy 0.18.2—afaik).
Fast forward some time, too: lemmy 0.18.4 comes out. I decide to upgrade to 0.18.4 from my existing 0.18.2.
I pull the git repo. Compile it locally. It goes well, no errors in the compilation process. I stop the lemmy systemd service, then I “mv” the compiled “lemmy_server” to /usr/bin dir.
I try to restart the now-upgraded lemmy systemd service. However, the systemd service fails.
I check the sudo journalctl -fu lemmy and I see the following error message:
lemmy_server[17631]: thread 'main' panicked at 'Couldn't run DB Migrations: Failed to run 2023-07-08-101154_fix_soft_delete_aggregates with: syntax error at or near "trigger"', crates/db_schema/src/utils.rs:221:25
I report this issue here: https://github.com/LemmyNet/lemmy/issues/3756#issuecomment-1686439103
However, after a few back and forths and internet search, I conclude that somewhere between lemmy 0.18.3 and 0.18.4, lemmy stops supporting psql <15. So, my existing DB is not compatible.
Upon my investigation on my VPS setup, I concluded that psql 15 is running, however, lemmy is using the psql 13 tables (I do not know if this is the correct term).
Now my question: is there a way to import the lemmy data I had in the psql 13 tables to a new psql 15 table (or database, I don’t know the term).
To make things hairier: I also run a dendrite server on the same VPS, and the dendrite server is using the psql 15 with psql 13 tables on the same database as the lemmy one.
The dendrite database is controlled by a psql user named “dendrite” and the lemmy database is controlled by a psql user named “lemmy” . I hope this makes differentiation between two databases possible. And so I do not harm my existing dendrite database.
Any recommendations about my options here?
user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/pg_dump --port=5432 lemmy > /home/user/lemmy_databackup.sql user@server:~$ ls -la lemmy_databackup.sql -rw-r--r-- 1 user user 56554817 Aug 23 00:59 lemmy_databackup.sql user@server:~$ ls -lah lemmy_databackup.sql -rw-r--r-- 1 user user 54M Aug 23 00:59 lemmy_databackup.sqlit’s plain text, I suggest grep against it for something you know is in there… that you created? Just to be sure when we do a restore against port 5433 we aren’t overwriting good data ;)
I grepped the exported sql file. I identified a long blog post of mine. So others should be there, too.
Ok, so now we restore to 15… double-check we have the port right for this…
Ok, so there is one issue we might run into. the lemmy user probably doesn’t exist on the PostgreSQL 15.3 install - so try these from the from-scratch install documentation:
sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "CREATE USER lemmy WITH PASSWORD 'db-passwd';" # maybe not needed with restore? sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "CREATE DATABASE lemmy WITH OWNER lemmy;" sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "ALTER USER lemmy WITH SUPERUSER;"Then to do the restore:
sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 --file lemmy_databackup.sqlThe restore may end up creating the lemmy user and a password for it, I’m not sure… so if you used different passwords for 13 and 15 it might have gone back to the 13 password for that user. Haven’t tested.
user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "CREATE USER lemmy WITH PASSWORD 'REDACTED';" [sudo] password for user: CREATE ROLE user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "CREATE DATABASE lemmy WITH OWNER lemmy;" CREATE DATABASE user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 -c "ALTER USER lemmy WITH SUPERUSER;" ALTER ROLE user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 --file lemmy_databackup.sql psql: error: lemmy_databackup.sql: No such file or directory user@server:~$ ls -la lemmy_databackup.sql -rw-r--r-- 1 user user 56554817 Aug 23 00:59 lemmy_databackup.sql user@server:~$ sudo -iu postgres /usr/lib/postgresql/15/bin/psql --port=5433 --file /home/user/lemmy_databackup.sql SET SET [...] [many many rows of output] [...] ALTER TABLE ALTER TABLE REVOKE GRANTok, so at this point your service file needs to have the correct LEMMY_DATABASE_URL environment variable, set to the PostgreSQL 15 install… 5433 port and correct password… and you should be able to start lemmy service and the migration should work this time… and you be up and running.
Can you give me the example for that directive? I can then modify it to my exact situation (password, etc.)
EDIT: Is it something like this? Environment=“LEMMY_DATABASE_URL=postgres://username:password:5432/lemmy”
I am not sure on the username:password part btw
https://join-lemmy.org/docs/administration/configuration.html
Going by your previous service config example…
Environment=LEMMY_DATABASE_URL=postgres://lemmy:password@lemmy_db:5433/lemmyWith 5433 on there instead of what most people use, 5432.
now the “lemmy_db” is a hostname, which I pulled from those docs, but probably just set to 127.0.0.1 (or “localhost”) instead of adding that to your hosts file?
But the port should be 5433, right?
I edited my reply…
now the “lemmy_db” is a hostname, which I pulled from those docs, but probably just set to 127.0.0.1 (or “localhost”) instead of adding that to your hosts file?
You can see the lemmy.hjson file I posted in this thread, I think it is just set to 127.0.0.1 in there