From: Dishayloo <Dishayloo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Problem accessing my databases after postgres was upgraded
Date: Wed, 27 Jul 2022 12:59:11 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38306@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
New issue by Dishayloo on void-packages repository
https://github.com/void-linux/void-packages/issues/38306
Description:
I regularly update my system with xbps-install -Suv. I noticed postgres wasn't working anymore and realized that I now have postgresql14 installed and the old postgres-Installation is gone. So I configured the new postgres to run with runit (which works) and wanted to convert my old data-dir. This is not working, apparently as the old postgres-Binaries are missing.
Here is my console attempt:
```
$ sudo su postgres
$ pg_upgrade -c -d /var/lib/postgresql/data -b /usr/lib/postgresql/ -D /var/lib/postgresql14/data
Prüfen von »/usr/lib/postgresql/postgres« fehlgeschlagen: keine reguläre Datei
Fehlgeschlagen, Programm wird beendet
```
The output is in german, but it basically means: check for »/usr/lib/postgresql/postgres« failed: no regular file; Failed, program is terminated
This is as the old postgres-binaries are not present anymore - or I don't know where they are.
next reply other threads:[~2022-07-27 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 10:59 Dishayloo [this message]
2022-07-27 12:04 ` Duncaen
2022-07-27 12:05 ` Duncaen
2022-07-27 12:07 ` Duncaen
2022-07-27 12:07 ` Duncaen
2022-07-27 12:57 ` Dishayloo
2022-07-27 15:10 ` Chocimier
2022-07-27 17:06 ` Dishayloo
2022-07-27 17:07 ` [ISSUE] [CLOSED] " Dishayloo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38306@inbox.vuxu.org \
--to=dishayloo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).