Github messages for voidlinux
 help / color / mirror / Atom feed
From: Dishayloo <Dishayloo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Problem accessing my databases after postgres was upgraded
Date: Wed, 27 Jul 2022 19:06:59 +0200	[thread overview]
Message-ID: <20220727170659.M11SuVruzpENfI94bgeNaGFTWaQ9vxSSvsD3LjnKQZo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38306@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

New comment by Dishayloo on void-packages repository

https://github.com/void-linux/void-packages/issues/38306#issuecomment-1197054438

Comment:
Thanks, these are helpful hints. I found my own solution though in the meantime. I found an older VM at work I could install Postgres 9.6 on, copy my datadir over and exported my databases with pg_dump and reimported them into psql14. So that solved it for me, but hopefully this will help others running into the same problems.

And I actually wasn't aware I was riding an outdated psql-installation and had the chance to port over to newer numbered versions. So the removal took me by surprise. I should have been more attentive to the installation, so that I would've noted it and did somethign then were was more time. But in the end I could find a solution and now know about the possibility for downgrading, which may come in handy in the future.

  parent reply	other threads:[~2022-07-27 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 10:59 [ISSUE] " Dishayloo
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 [this message]
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=20220727170659.M11SuVruzpENfI94bgeNaGFTWaQ9vxSSvsD3LjnKQZo@z \
    --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).