From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "W(dot)P(dot)" <laurentp(at)wp(dot)pl>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Problem with PG 11 database on OrangePi3 (ARMBIAN, ARM64) after disk disrupion (problem with USB disk connection) |
Date: | 2022-04-06 18:09:25 |
Message-ID: | 425a7834-a132-2ef8-e199-ea6c088b3ac6@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/6/22 11:04 AM, W.P. wrote:
> W dniu 06.04.2022 o 18:54, Ron pisze:
> I know about restoring backup. I just don't have one (at least with
> reasonnable age), as it is experimental installation. (Didn't ever been
> thinking about locating production DB on USB drive :) ).
>
If it is experimental you could try pg_resetwal:
https://www.postgresql.org/docs/11/app-pgresetwal.html
Read all the way through for the ifs/ands/buts.
> If it is not possible to get rid ("somehow") of this "replication
> error", I will do a "logic restore" -> I have similar database on my
> laptop, so I'll get a pg_dumpall from this one, then recreate fresh DB
> on OPi and restore from SQL.
>
>
> It looks that DATA in PG DB is protected by various mechanisms very
> well, but "dictionary data" (in this case replication data) is not (as
> much). And in my case ext4 recovery mechanisms failed.
>
> This makes me logical replication more appealing.
>
>
> Laurent
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bisnett | 2022-04-06 22:13:24 | Per-Table vacuum_freeze_min_age |
Previous Message | Ray O'Donnell | 2022-04-06 18:06:13 | Re: Problem with PG 11 database on OrangePi3 (ARMBIAN, ARM64) after disk disrupion (problem with USB disk connection) |