From: | Muhammad Imtiaz <imtiazpg712(at)gmail(dot)com> |
---|---|
To: | Mahendra Singh <msmahendrasingh18(at)gmail(dot)com> |
Cc: | Jean-Paul POZZI <jp(dot)pozzi(at)izzop(dot)net>, vrms <vrms(at)netcologne(dot)de>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: WAL file corruption on standby PostgreSQL |
Date: | 2024-07-23 11:29:58 |
Message-ID: | CACW1Ly144u0zxy64ugExDfQNMXEpurpY7PRLRvXz3=P_9a9jaQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
Consider the pg_rewind utility to synchronize the standby with the
primary node, ensuring the primary node is in a consistent state.
*Muhammad Imtiaz*
*PostgreSQL Technical Support Lead *
*/ Pakistan R&D*
*Mobile: +923345072521*
*Email: imtiaz(dot)m(at)bitnine(dot)net <imtiaz(dot)m(at)bitnine(dot)net>*
On Tue, Jul 23, 2024 at 11:50 AM Mahendra Singh <msmahendrasingh18(at)gmail(dot)com>
wrote:
> Try to reset the wal using '*pg_resetwal*'.
>
> https://www.postgresql.org/docs/current/app-pgresetwal.html
>
>
> On Tue, Jul 23, 2024 at 2:20 AM Jean-Paul POZZI <jp(dot)pozzi(at)izzop(dot)net>
> wrote:
>
>> Hello,
>>
>>
>>
>> Some traces in Postgres or system logs ?
>>
>>
>>
>>
>> ------------------------------
>> *De:* "vrms" <vrms(at)netcologne(dot)de>
>> *À:* "undefined" <pgsql-admin(at)lists(dot)postgresql(dot)org>
>> *Envoyé:* lundi 22 juillet 2024 21:26
>> *Objet:* Re: WAL file corruption on standby PostgreSQL
>>
>> On 7/22/24 8:42 PM, Muhammad Ikram wrote:
>>
>> >> Also try to see what caused corruption of WAL archives.
>>
>> out of curiosity ... any hint in how to approach this?
>>
>>
>>
>> On 7/22/24 8:42 PM, Muhammad Ikram wrote:
>>
>> Hi Wasim,
>>
>> IMO, you will have to rebuild the standby server by taking base backup
>> from Primary and copying it to standby, restart standby. Also try to see
>> what caused corruption of WAL archives.
>>
>> Regards
>> Muhammad Ikram
>>
>>
>> On Mon, Jul 22, 2024 at 11:26 PM Wasim Devale <wasimd60(at)gmail(dot)com> wrote:
>>
>>> Hi All
>>>
>>> 2024-07-22 11:15:10 PDT [1723]: [7028-1] user=,db=,app=,client= LOG:
>>> restored log file "000000010000170900000081" from archive
>>> 2024-07-22 11:15:10 PDT [1723]: [7029-1] user=,db=,app=,client= LOG:
>>> invalid resource manager ID 128 at 1709/8183BFA8
>>> 2024-07-22 11:15:10 PDT [1723]: [7030-1] user=,db=,app=,client= LOG:
>>> invalid resource manager ID 128 at 1709/8183BFA8
>>>
>>>
>>> I got this error and the replication has stopped. Please suggest about invalid
>>> resource manager ID.
>>>
>>> Thanks,
>>> Wasim
>>>
>>
>>
>> --
>> Muhammad Ikram
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-07-23 12:20:59 | Re: Pg_repack |
Previous Message | Laurenz Albe | 2024-07-23 09:51:10 | Re: Pg_repack |