Do you need any additional information?
-Original Message-
From: Lahnov, Igor
Sent: Friday, September 30, 2022 10:18 AM
To: 'Michael Paquier'
Cc: Kyotaro Horiguchi ;
pgsql-general@lists.postgresql.org; Timonin, Alexey
; Dmitriyev, Andrey
Subject: RE: Streaming wal fr
>> Which version of PostgreSQL are you using? There has been a few commits
>> around continuation records lately, so it is hard to say if you are pointing
>> at a new issue or if this is a past one already addressed.
Hi Michael,
We are using PostgreSQL 14.4.
Primary_conninfo is set in postgresql.conf
The reason is definitely something else, we do not know what. This is fatal in
this case.
> 2022-09-26 14:08:24.366 [3747796] LOG: invalid record length at
> 1473/A5FFEE08: wanted 24, got 0
> 2022-09-26 14:08:24.366 [3747796] LOG: invalid record length
Hi,
After failover all stand by nodes could not start streaming wal recovery.
Streaming recovery start from 1473/A500, but standby start at
1473/A5FFEE08, this seems to be the problem.
What can we do in this case to restore?
Is it possible to shift wal streaming recovery point on primary?
Can
As far as I understand, according to the logs, the last leader does not yet
know about the new timeline
and it is trying to download the full log from the previous timeline.
It seems there should be a conflict that the partial file already exists
locally when restoring in this case, but this does
I can't answer your question. What do you think, the recovery from the archive
should work in this case?
1. the partial file should not be restored at all cases
2. the partial file should recover as a partial and replace the local partial
3. recovery command, should return a conflict - file alread
Hi,
Yes, the *patial* from the *new leader* is restored to *last leader* and
renamed to 0002054E00FB, without *partial* postfix.
>>Postgres asks for file 0002054E00FB but somehow gets
>>0002054E00FB.partial instead. Why?
Yes, Postgres asks for 0002054E
We know what the problem is, but don't know how to solve it correctly.
After failover, *new leader* promoted and read local partial log to LSN
54E/FB348118
->
2022-05-23 01:47:52.124 [12088] LOG: record with incorrect prev-link 0/100 at
54E/FB348118
2022-05-23 01:47:52.124 [12088] LOG: redo don
What additional information is needed?
Hi,
We're using asynchronous streaming replication together with WAL archiving and
recovery (we've set these parameters: archive_command, restore_command,
recovery_target_timeline=latest).
To manage backup and recovery, we're using pg_probackup.
We have a 3-node cluster managed by Patroni on Raft
10 matches
Mail list logo
