W dniu 06.04.2022 o 18:54, Ron pisze:
> On 4/6/22 11:41, W.P. wrote:
>> W dniu 06.04.2022 o 12:37, Laurenz Albe pisze:
>>> On Wed, 2022-04-06 at 10:57 +0200, W.P. wrote:
>>>> Is it possible to repair this?
>>> Not unless you tell us what exactly you did, command by command.
>>>
>>> Yours,
>>> Laurenz Albe
>>>
>>>
>>>
>> That was not a "command". PG was working ok, DB on encrypted (LUKS on
>> LVM2, ext4) USB drive.
>>
>> Then simply I disconnected cable by accident.
>>
>> After OPi restart, with filesystem on USB mounted again and fsck'ed
>> first, PG refuses to start. With a message about replication error in
>> log.
>>
>> But I did not configured relication.
>
> The disk got corrupted, and one part that got corrupted is where
> Postgresql's replication (or not) is configured.
>
> Delete the data/ directory and restore from backups (including config
> files).
>
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 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
